3 ms·
with lambdalith you miss out on some things like granular IAM roles and granular Memory/Cores config. Also with lambdalith you probably end up needing an applic
by mastazi 3y ago
with lambdalith you miss out on some things like granular IAM roles and granular Memory/Cores config. Also with lambdalith you probably end up needing an application framework as opposed to just using mostly vanilla features of your language of choice. Of course I agree that lambdalith has advantages as well.
- kikimora 3y agoI don’t buy this. From the top of my head I can think of many things not handled by the Lambda runtime: session cookies, routes with ids in them like /author/15/posts, having to specify Content-Type for responses, generating error responses properly, etc. Good server framework does this for you transparently.
- mastazi 3y agommm sure but I never said that the Lambda runtime handles those things... By the way, routes with ids are handled no problem by API Gateway, you can even set more complex ones like {proxy+} etc.
- kikimora 3y agoMy comment mostly relates to this > Also with lambdalith you probably end up needing an application framework as opposed to just using mostly vanilla features of your language of choice. The point I make is even with lambda per endpoint you need many framework features.