Production-Ready Microservices

I required to understand (from management position) how to get a major system utilizing microservices to production. Granted, I have tech background, but this book covered it from A to Z for me. Recommended reading both for tech leads and technical managers.

If you have worked on a service team, you probably know everything in this book already. Great for junior developers ramping up though. The continuous theme of the book is written prioritizing availability. This could also be a good handbook or reference for a manager, PM, or intern. Pros: The book is well written and easy to read. It addresses the organizational impact of microservice architecture. I'm working on a service team, but it's not yet large enough to adopt a microservice architecture. I like that the book addresses the evolution of from monolith to microservice, and how starting from scratch as a microservice isn't exactly a cost efficient plan either. Thinking about a dependency graph for a product running on microservice architecture is also interesting. I like her introduction of the qualitative and quantitative scale factors. Cons: This book is a little bit basic. I was hoping it would be more about software design patterns for microservices.

Very interesting. I've worked in the computer field for 40 plus years and have seen a lot of changes during that time. I must say that IoT and it's applications are extremely exciting. This is an excellent book on Microservices.

Good overview of micro-services ecosystem, challenges and ways to make it more stable. Would love to see more in depth and concrete examples and a little less repetition.

The book is really a description of what I would call a quality assurance framework for a microservices environment. Compared to its modest length, it contains quite a number of useful ideas from someone in the trenches.

I've been working in organizations trying to adopt Microservice architecure for a few years and each has faced many issues and have had different degrees of success. One of the largest issues is standardization and putting in place processes that ensure Microservices are truly ready for production. This book addresses many of those issues and does it using actual use cases. It covers what it means for Microservices to be ready for production. It offers practical advice that organizations can adopt, or at least think about. I definitely recommend this to anyone working in an environment where Microservices are being used (either from splitting a monolithic application or building services from the start).

This book is perfect for people in software management roles. It's a short read at about 130 pages but covers all the important high-level topics at just enough detail for someone like myself. The larger book, Building Microservices, seems perfect for those in an individual contributor role.

Great read with great tips to help get you put in the right direction if you're thinking about moving towards microservices.

Os microserviços estão se tornando cada vez mais populares entre as empresas que buscam aumentar a agilidade e a escalabilidade de seus sistemas. No entanto, para que os microserviços sejam realmente úteis, eles precisam ser produção-prontos. A construção de sistemas padronizados é uma parte importante do processo de tornar os microserviços prontos para produção. Isso envolve definir padrões para a arquitetura, o código, os testes e o monitoramento. Esses padrões permitem que os desenvolvedores criem microserviços consistentes e confiáveis ​​que podem ser implantados com segurança em ambientes de produção. Além disso, a padronização dos sistemas também pode ajudar a reduzir o tempo de desenvolvimento e manutenção dos microserviços. Ao definir padrões para o código, os desenvolvedores podem reutilizar componentes existentes e evitar a necessidade de recriar o mesmo código para cada novo microserviço. Isso significa que os microserviços podem ser criados mais rapidamente e com menos esforço. Portanto, a construção de sistemas padronizados é uma parte essencial do processo de tornar os microserviços prontos para produção. Ao definir padrões para a arquitetura, o código, os testes e o monitoramento, as empresas podem garantir que seus microserviços sejam consistentes, confiáveis ​​e prontos para produção.

The author states that this is not a reference book, nor a tutorial on how to build production-ready microservices. What it is is an excellent manual on what topics need to be discussed, what corporate structures may need to be built and what technical architecture might need to be designed when you are considering, or implementing your own microservices, and at that it excels. I work in a company that started laying the groundwork for microservices two years ago by implementing an infrastructure - based on mesos - that puts the deployment pipeline under the control of the development teams. This book has been an invaluable insight into illuminating some possible reasons things are how they are and what decisions need to be taken when building our service. The book is structured with overview introductory chapters laying out the areas each of which are expanded on later in the book in separate chapters. This structure makes the book useful for developers/devops - who should read the whole book - and business/management people who should at least read the overview chapters. All in all a very useful book that should be read by all members of the development and business team in your company if you are considering using microservices extensively. It is important that everyone understands the challenge and has a good mental model of what is required. This book provides that.

So far I like it. Like experience sharing. As if you talk to a person and she'd would be sharing her experience with you. This kind of format. Sure it maybe not that useful for the expert. But there are not that many experts in this area. So it's useful for beginners and intermidate guys. I would say for 95% ppl would think he may be interested in it.

Really great book. Practical view of what it takes to run microservices in production. Only flaws are no mention of security, and no real discussion on how to implement this checklist process in a continuous delivery model. Checklist is great, but when you are incrementally building/shipping your service from scratch, when/how often should you audit?

I've read a few books on microservices, and most of them promote the concept, but don't offer much help beyond that. This is the first one that gives me really practical advice on running a reliable large scale deployment, and I would recommend it to anyone who is responsible for keeping a microservice-based system up and running.