3 ms·
Much of the argument here is that serverless means breaking your codebase up into lots of serverless functions that act independently. Yes that would be comple
by andrewstuart 9y ago
Much of the argument here is that serverless means breaking your codebase up into lots of serverless functions that act independently. Yes that would be complex.
So, don't break the code up.
I've built several AWS Lambda applications, all as one big monolithic Python application - there's just one serverless function. Works fine. Super simple.
- zackify 9y agoSame here, but using express.js. People seem to think you have to make a new function for any little piece of your api
- andrewstuart 9y agoAnd if you did that, then you'd have a nightmare keeping them all warm.
- viraptor 9y agoOn the other hand, once you break the process into many parts, you don't have to keep most of them warm. Responding to some backend events - who cares? Some timer, or message, or whatever will fire up a couple seconds later and that's often completely fine. It's normally the user-exposed parts that need warming up.
- woutr_be 9y agoDoes that mean you just build your express api as usual and run it on Lambda without any issues? We run a few functions that could perfectly act as a single api.