Microservices are not classes and Object Oriented Programming should not be used for designing systems
tl;dr: when decomposing your business domain into microservices, use techniques like Domain-Driven-Design or Volatility-Based-Decomposition. Don’t just create a microservice for each domain entity and call it a day....
Microservices Layered Architecture: because not all events are created equal
In this post, we’ll discuss the coupling between services and dependency management. Take, for example, the two diagrams below: which design looks more maintainable? Even without knowing what the system does and what the...
Vertical Decomposition: Creating Cohesive Services
If you are software developer, architect, or manager, without a doubt you must have heard about the benefits of microservices architectures. There are clearly disadvantages when it comes to microservices architectures, but...
Add git-like functionality to your application using Event Sourcing
In this post we’ll implement a tool for managing products using event sourcing, node.js and neo4j. Event sourcing will enable us to support neat git-like features such as versioning, branching and merging that would be very...
Integration Patterns for Microservices Architectures: The good, the bad and the ugly
In this post we’ll discuss different integration patterns for synchronizing information between microservices. One of the advantages of more traditional architectures, where all the application’s data is stored in one...