How to Implement SOA
Series of posts, in a single place
Here is a list of my posts about implementing SOA.
First, these are the theoretical basics.
- Why should you split a monolith? I guess you already know why, but just to refresh.
- Wrong Ways of Defining Service Boundaries. There are plenty of them, and they are really widespread.
- What Characteristics My Services Should Possess
- How to Define Service Boundaries. That’s the crux of the whole series.
The next post is for DDD-practitioners about how to define a bounded context: DDD Strategic Patterns: How To Define Bounded Contexts.
After that, what to watch out for the most when implementing concrete services: Why Microservices Fail.
Then, some examples.
- Example of Service Boundaries Identification, in payment service provider’s area. This post contains some thoughts on scaling, sagas, aggregate boundaries, composite UI and CQRS.
- Service boundaries identification example in e-commerce. More common area, with some tips on correct boundaries identification.
- Event-Driven Architecture Implementation. That’s more lower-level example, with RabbitMQ specifics.