I’m a big fan of so-called serverless architectures. The idea of these products is that developers don’t have to think about spinning up servers to do some processing—rather a construct that goes something along the lines of “when trigger A happens, set off process B, and when process B is complete, your job is done” can be enabled.
Amazon Web Services (AWS) was the first of the public cloud vendors to launch a serverless offering, AWS Lambda. Since then, it is an approach other players have followed.
But while serverless offerings add massive value in terms of simplicity and economics, they provide challenges. The servers that run the actual code to process these events are not exposed to developers. As such, developers have zero visibility into how those servers are working and what they’re up to.