Grigor, thank you for a necessary and well-written article.

Our profession is full of these simple, but misunderstood "principles". Software architecture and design are really an exercise in finding the appropriate compromises among competing requirements. They should not be about slavishly following a misunderstood "principle".

https://medium.com/nerd-for-tech/getting-architecture-right-part-2-327dd3fa41a3

One of my pet peeves is the misunderstanding that each service should have its own unique database, when the real constraint is far more practical and useful:

https://drive.google.com/file/d/1-YEYtS1rqmaeKZti9dqKgGYl5NXZs3wT/view