When it comes to "9 best practices for developing microservices", I'd add:

0. Do I really need microservices to solve my problem and can I start with a modular monolith instead?

Expand full comment

About the "9 best practices for developing microservices" and the Single Responsibility principle

Some times you have to do it a packaging level instead of a microsservice level. Why? Communication between services take time, at least some milliseconds, so it could increase your latency

Expand full comment

Also all of the serialization and deserialization between each service, usually the overhead is not much but it all adds up with you have lots of calls/services!

Expand full comment

I love the visual representation of the Code Review Pyramid. I don't have any new questions to add, but if anyone wants a bit more detail I recently wrote up a short three-parter on code reviews (aimed at early-career engineers).




Expand full comment