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…)
5
10
3
36
Next step will be to visualize serverless functions 🤧
1
I've already had that question. 🤣
1
Related. I have a really hard time with splitting my domain into so tiny deployment boundaries. How to keep cohesion and overview?
2
Replying to @jeppec @simonbrown
If it hurts, maybe don’t do that :)

Nov 14, 2018 · 7:39 AM UTC

2
2
Replying to @stilkov @jeppec
That was my knee-jerk reaction, but I thought I'd ask more questions first! Although we're often told, "if it hurts, do it more often"... 😄
more replies
Replying to @stilkov @simonbrown
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.
1