Ask HN: Please recommend a serious book on Microservices | Hacker News Reader

Ask HN: Please recommend a serious book on Microservices

40 pointskosolam13 comments

What would be a good book to learn from the experience of others the best practices around Microservices design, implementation and production life cycles (deploy, upgrade, etc)

View on HN

Microservices Patterns by Chris Richardson is a great read. It takes the idea of design patterns and applies it to designing and implementing a microservice architecture. The idea is that you may already be doing some of the things that the book suggests but now you know the name for it and you have some pretty opinionated advice from the author about how to do it. It's a long book but it captured my attention from start to finish and was useful pretty much immediately.

Overall I'd say the best book about microservices is Chris Richardson's Microservices Patterns (https://www.manning.com/books/microservices-patterns). That book will get you covered with everything you need to know about designing and building microservices, and also the various strategies you can use to integrate them. The examples are in Java, but even without being a Java dev it shouldn't be difficult to follow.

I'd still recommend Sam Newman's classic Building Microservices (https://www.oreilly.com/library/view/building-microservices/...) as it describes very clearly the main principles for designing robust microservices architectures. If you wanted to learn how to migrate a monolith to a microservices architecture, you can also checkout Newman's more recent Monolith to Microservices (https://www.oreilly.com/library/view/monolith-to-microservic...).

If you want a more practical approach with JavaScript examples, I'd recommend Ashley Davis' Bootstrapping Microservices with Docker, Kubernetes, and Terraform (https://www.manning.com/books/bootstrapping-microservices-wi...).

Finally, if you wanted a practical approach with more emphasis on API integrations and examples in Python, I'd recommend Microservices APIs in Python (https://www.manning.com/books/developing-microservice-apis-w... - disclosure - I'm the author). You can download two free chapters from this URL: https://www.microapis.io/resources/microservice-apis-in-pyth...

It goes without saying that there're a lot more resources about microservices, and many of them excellent, but these are the books I'd recommend to get started.

Forgot to say, you should also check out Chris Richardon's excellent website dedicated to microservices: https://microservices.io/

This is not a book but a well-maintained and documented open source sample by the Google Cloud Team of a cloud-native application with "10 microservices showcasing Kubernetes, Istio, gRPC and OpenCensus"

https://github.com/GoogleCloudPlatform/microservices-demo

Not a book but have you looked into

Microservices with Node JS and React by Stephen Grider

Microservices is a complex topic it will be very hard to learn by following a book. If you really want to learn about Microservices start looking for a job.

I recommend "learning microservices 2nd edition". The first edition is good, the second gives more practical advice.

Who is that by and what is the precise title? A quick search didn't reveal a book called "learning microservices" but I may be missing something obvious.

I think OP meant "Building Microservices" by Sam Newman.

ops, my bad. that's exactly what I meant. Thanks for the correction

Mannign's Microservices in action could be what you're looking for https://www.manning.com/books/microservices-in-action

They also have one on microservices patterns.

Sam's book is great; v2 in August https://samnewman.io/books/building_microservices_2nd_editio...

Microservices in Action by Morgan Bruce and Paulo A. Pereira.

Very good book not only in theory but with practical examples. Covers desing, deployment, observability and so on.

You don't need a book, just know that every class and module should be split up into a separate microservice. To communicate with your microservice, a brittle approach is recommended.

Reply on news.ycombinator.com