Of course there is also a general introduction into microservices that all readers can benefit from. And some of the projects cover technologies for monitoring, logging, or tracing which is valuable for operations. Developers can deep dive into the technologies with the provided sample projects. Architects learn to understand the technology landscape and its implications. Wolff: As the focus is on technologies, architects, operations, and developers benefit from the book the most. InfoQ: Who’s the target audience of the book and how can they benefit from reading it?
DOCKER AND KUBERNETES THE PRACTICAL GUIDE FREE
You can now find the basic in the free booklet "Microservices Recipes". That is how I started working on the book. So it was time to write a book about the technology landscape to complement the first book. However, with the growing popularity of microservices, more and more technologies appeared that support microservices. Then I condensed the basic architecture ideas into the free Microservices Primer. It had only one chapter about technologies. InfoQ: Why did you decide to write this book on the Microservices field at this stage? Did you find a missing piece of the puzzle?Įberhard Wolff: When I started to write this book, I had already written a book about microservices with a focus on architecture. Targeted to architects, developers and operations, it provides a set of technology recipes along with executable samples that can be used to address different needs. The book “ Microservices, a Practical Guide, Principles, Concepts and Recipes” by Eberhard Wolff explores technology stacks for microservices-based architectures that can be used at the overall system level.
0 kommentar(er)
