Microservices is a sexy concept, but for quite a long time, I don’t exactly know what it is, and how it work to help my daily job, read this book for clarify it. This book is a guidance, not a practice, most suit for reading by architect and develop manager
What is Microservices? from wikipedia:
A microservice is a software development technique — a variant of the service-oriented architecture (SOA) architectural style that structures an application as a collection of loosely coupled services. In a microservices architecture, services are fine-grained and the protocols are lightweight. The benefit of decomposing an application into different smaller services is that it improves modularity and makes the application easier to understand, develop, and test and more resilient to architecture erosion. It parallelizes development by enabling small autonomous teams to develop, deploy and scale their respective services independently. It also allows the architecture of an individual service to emerge through continuous refactoring. Microservices-based architectures enable continuous delivery and deployment.
Microservices seems like a technical architecture more prevail at Java and .net community, which particularly suit for giant project, as author’s opinion, he advocate SOAP and XML to JSON, I think model level scalable project need microservices too, which need a simple version(JSON+API), I would try one day
To microservices, micro is important, but how micro is micro? I like this metaphor in this book:
a microservice as something that could be rewritten in two weeks, a rule of thumb that makes sense for his particular context.
A video introduce what is microservices:
