4 ms·
Others mentioned things related to cost, but for me the best thing is the simplification of the design. Usually you have to decide many things up front - is som
by viraptor 9y ago
Others mentioned things related to cost, but for me the best thing is the simplification of the design. Usually you have to decide many things up front - is something asynchronous, is it queued, is it behind a specific API, etc. Once you start using lambda, many of those questions get much simpler - that thing you're thinking of now is just another lambda function. You can change many details later. Even better - you can move functionality between subprojects without reintegrating code most of the time - lambda design guarantees you have completely isolated self-contained units of functionality.
It does not solve all the issues. And you can potentially split the problem into too many tiny parts, but the "just make it another function" approach worked for me as a rule of the thumb.