4 ms·
> But if your microservice is ThatOneCatOnMyBlock(), it might be a sign that you have broken things down too far. This is what I commonly see Lambda turn into
by easton 3y ago
> But if your microservice is ThatOneCatOnMyBlock(), it might be a sign that you have broken things down too far.
This is what I commonly see Lambda turn into and why I think it's real messy. People think that adding another Lambda is as cheap as adding a function in regular code and put them everywhere. I haven't seen it as much with microservices, might just be where I work though.
Cloudflare workers had a interesting solve for this where they don't let you make a http request to another worker, they mount the code for that worker in the same process. Kind of wish AWS could find a way to do that, although since they support multiple runtimes I don't know if it is possible.
- asimpletune 3y agoExactly, except a tiny correction. Instead of process it's "io context", and you can make requests to other workers if they're in a separate zone.
- rjrodger 3y agoWell each of our microservices is also a Node package, so we also do that ourselves for the Lambda deployments - load 'em all up in the one Lamdba!