I keep getting asked how to diagram a microservices architecture, especially when the diagram becomes very cluttered. Option 1: partition the single diagram into many (one per business area, etc). Option 2: create an alternative visualisation (e.g. structurizr.com/share/4241/e…)

Next step will be to visualize serverless functions 🤧

I've already had that question. 🤣

Related. I have a really hard time with splitting my domain into so tiny deployment boundaries. How to keep cohesion and overview?

If it hurts, maybe don’t do that :)

I’ve tried the mental exercise of doing it and I very run into the need to include the same code with different functions (eg aggregate invariants). Seems like splitting atoms.

So I’m wondering if there’s something I’m missing in the process?

I’ve never bought into the “tiny” variant of microservices, so I’m the wrong person to comment

Me neither. I think the message is that deployment and scalability of serverless functions is so easy that it shifts the balance towards nanoservices. Not convinced though /cc @arnonrgo

Serverless is also good from a cost perspective ... "self-provisioned CGI for the cloud era". ;-)