Stateless Services — and Performance
So, you’ve drunk the ServerLess Kool-Aid — Lambda / Azure Functions / GCF / whatever — and are frenetically converting all your micro-services to StateLessMicroServices™, right? And everything is just going to be peachy-keen, right? Well, maybe. As you go down the path, one of the things you might find is that you now have different performance issues that you need to pay attention to. (•) In particular • Resources : Yeah, you’re going to have to open/clean-up those db connections, file handles and network connections each time. • State : is now going to be in your data-store. And oh, you do have a data-store right? Which you are dealing with per -1- above, right? Which means you’re going to have to retrieve/store it each time you run your function… • Concurrency : Yup, welcome to the world of concurrency. You’re going to have to deal with your serializability, linearizability, consistency, and that entire ball-of-wax...