Hacker News new | past | comments | ask | show | jobs | submit login

> I have been thinking about this a lot, and it could work if being locked into AWS is considered an acceptable risk.

This is a huge risk. If they shut you out, for whatever reason, you're done. You can't port your code to somewhere else. It's Lambda specific.




>You can't port your code to somewhere else. It's Lambda specific.

is that really true tho? Its just a function that does work from a request and send the result off to some where else.


You won't be able to port it without any additional work, but if you are willing to do some refactoring (specifically removing the Lambda-specific objects, etc) then it can run anywhere. Of course the time this will take depends on the size of the project, but it can be definitely done without rewriting the whole application, but just rewriting the "invoker" part.

To make a future port easier, the functions could also be modularized by keeping the real business logic and the Lambda integration separate, but integrated.


how many Lambda-specific objects are there besides the context promise?




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: