Some AWS FaaS Unknown Points

When interacting with lambda we got sometime tired of microservice developed on serverless and their problems , when challenging with others i found that there are the unknown possibilities which drive them to frustrating solutions by using extra and overkill tasks, like publishing the lambda versions from CI , Duplicating Lambdas to have multiple versions and ……..

Some Points:

• Lambda can have multiple versions running

Add alt text

• you can have a canary load between lambda versions using aliases

Add alt text

• you can have a lambda with multiple handler names s for each one

Add alt text

and other version as

Add alt text

so you can let your function be as a part of your Rest API and handle invocations by ALB or ApiGateway as

/api/v1/xxxx

/api/v2/xxxx

• You can have multiple runtimes for a lambda function for each version separately as Nodejs , .NetCore or Go

Conclusion:

The lambda versions are the separate and totally independent components of your lambda , so you can this about as a separate lambda logically which can help your to organize your functionality properly and efficiently .