You start building a beautiful monolith system. Maybe a modular monolith. The system grows, and requirements are ever-changing. Slowly, cracks begin to appear in the system. This could be for organizational reasons and distributing the work across a team. Or it could be because of scaling issues and performance bottlenecks. You begin the process of evaluating the benefits and tradeoffs of possible solutions. At last, you come to a decision. It's time to migrate parts of the system to individu...| www.milanjovanovic.tech
When—and when not—CDC can break encapsulation, whether it matters, and strategies for avoiding these problems when it does happen.| www.decodable.co
Modeling your domain as timelines instead of object graphs| ismaelcelis.com
How to split up your large, complex, frontend codebases into simple, composable, independently deliverable apps.| martinfowler.com
Going directly to a microservices architecture is risky, so consider building a monolithic system first. Split to microservices when, and if, you need it.| martinfowler.com
Systems are constrained to follow the communication patterns of their designers.| martinfowler.com
CQRS (Command Query Responsibility Segregation) is the notion that you can use a different model to update information than the model you use to read information| martinfowler.com
There are problems with the centralized data lake. A future data mesh needs domains, self-service platforms, and product thinking.| martinfowler.com
What's the consequences of stress and how to manage it as a developer? Let's review some important and actionable tips.| The Valuable Dev
