Book Review: Microservices vs. Service-Oriented Architecture by Mark Richards

 I wanted to freshen up my knowledge on Microservices and when I was looking for resources to study, I came across this book. I'm glad that I found this.

Microservices has been trending subject for the past few years and Service-Oriented Architect has been there for a long time. If you like to know the differences between these two approaches and even learn several unknown topics with regards to these two architecture approaches, this will be a good book.

Microservices vs. Service-Oriented Architecture by Mark Richards was published in November 2015. There are few other books that are closely related to this book. Those are  Microservices AntiPatterns and Pitfalls and Software Architecture Patterns. Microservices AntiPatterns and Pitfalls is also free to download. The author has published many other books that are not free and I'm certain that they are worth the cost. Hoping to buy a few of them in the future.

The name of the book very briefly explains the content of the book. Before going into comparing the two architectural approaches, the author explains both approaches in areas such as communication protocols, modularity, service contract, service availability, and security. I personally learned several things that I didn't know about service-based architecture. The author doesn't dig deep into these topics, but for someone new, this will be a good starting point.

Next, the author talks about Service Characteristics and compared the architectures based on Taxonomy, Team ownership, and coordination, and Granularity. In this section, he talks about how services are categorized based on service type and business area, how development teams handle the development of services, and how to divide your application into smaller services.

In the next two chapters, he compares the Architecture Characteristics and Architecture Capabilities between SOA and Microservices. The chapters are divided into topics such as Component Sharing, Accessing Remote Services, Application Scope, and Contract Decoupling.

The book contains only 5 chapters including the summary.

Even though the book is small, compact and contains a few chapters, it will help you get started with your microservices studies, especially if you are from an SOA background. The author covers lots of topics with enough details to get you started. But if you want to gain more knowledge, you will have read other books that dig deeper into those topics.

You will be able to learn a lot without paying a penny and we are thankful to the author and the company for sharing the knowledge with us.

Other from the Author:

Note: This is my first attempt at writing a book review. Please leave your feedback in the comments sections.