3 ms·
> which includes your API, Middle ware and then Database Layered microservices are an antipattern. In most cases, functionality is best divided by domain.
by bencollier49 7y ago
> which includes your API, Middle ware and then Database
Layered microservices are an antipattern. In most cases, functionality is best divided by domain.
- thinkharderdev 7y agoThis is why I struggle with microservice architectures. It seems like there is a basic contradiction. On the one hand, it's vitally important that the microservices are carved into the correct modules otherwise you get a nightmare of operational complexity where simple functional changes require coordinated changes across multiple services. But defining the correct way modules requires a bird's-eye architectural view of the entire system, which seems contradictory to idea of self-organizing, independent teams. I can see how it works when the right way to divide things up is obvious or when you are dealing with IaaS or PaaS services, but in a complex business domain who decides how to carve things up?
- marcosdumay 7y ago> In most cases, functionality is best divided by domain. So, SOA?