✳flâneur — a map of the web's best reading

Microservice Trade-Offs

martinfowler.com · 3,903 words · saved by 1 readers

Many development teams have found the microservices architectural style to be a superior approach to a monolithic architecture. But other teams have found them to be a productivity-sapping burden. Like any architectural style, microservices bring costs and benefits. To make a sensible choice you have to understand these and apply them to your specific context. 01 July 2015 MICROSERVICES Microservices provide benefits… …but come with costs Summing Up The first big benefit of microservices is strong module boundaries. This is an important benefit yet a strange one, because there is no reason, in theory, why a microservices should have stronger module boundaries than a monolith. So what do I mean by a strong module boundary? I think most people would agree that it's good to divide up software into modules: chunks of software that are decoupled from each other. You want your modules to work so that if I need to change part of a system, most of the time I only need to understand a small par

Microservice Trade-Offs Microservice Trade-Offs Many development teams have found the microservices architectural style to be a superior approach to a monolithic architecture. But other teams have found them to be a productivity-sapping burden. Like any architectural style, microservices bring costs and benefits. To make a sensible choice you have to understand these and apply them to your specific context. Martin Fowler 01 July 2015 microservices Microservices provide benefits… Strong Module Boundaries : Microservices reinforce modular structure, which is particularly important for lar

Explore this link on the map →

related reading