Название: Enabling Microservice Success: Managing Technical, Organizational, and Cultural Challenges (Final)
Автор: Sarah Wells
Издательство: O’Reilly Media, Inc.
Год: 2024
Страниц: 300
Язык: английский
Формат: pdf, epub (true)
Размер: 10.1 MB

Microservices can be a very effective approach for delivering value to your organization and to your customers. If you get them right, microservices help you to move fast by making changes to small parts of your system hundreds of times a day. But if you get them wrong, microservices will just make everything more complicated.

In this book, technical engineering leader Sarah Wells provides practical, in-depth advice for moving to microservices. Having built her first microservice architecture in 2013 for the Financial Times, Sarah discusses the approaches you need to take from the start and explains the potential problems most likely to trip you up. You'll also learn how to maintain the architecture as your systems mature while minimizing the time you spend on support and maintenance.

Microservices are simple in concept, but the devil is in the details. There are so many aspects to getting the most out of this style of architecture, while also dealing with the complexity it brings. The problem is, getting the most out of microservices often is about nuance. The development of any software-based system requires people and technology coming together, and with microservices the people and organizational aspects are often greatly overlooked. People assume the answer must be a new programming language, more Kubernetes clusters, or perhaps a new vendor. But this approach results in an orgy of technological overload that ends up looking at less than half of the story.

For a microservice architecture, rather than deploying all the code for your system as a single monolithic executable, you split your code across multiple services that can be deployed independently. This allows you to release code for just one service, as soon as it’s ready, and gives you flexibility in how you build each service.

A microservice architecture is a distributed architecture. Each microservice runs in its own process, which means that what would be a method or function call within a single process in a monolith now goes over the network. This provides a clear boundary, making it hard to accidentally couple parts of the system together. However, calls over the network are much more likely to fail than those that are in-process. You can’t assume that the service you are calling will always be accessible and ready to serve your requests as quickly as you might like.

With this book, you will:
• Learn the impact of microservices on software development patterns and practices
• Identify the organizational changes you need to make to successfully build and operate this architecture
• Determine the steps you must take before you move to microservices
• Understand the traps to avoid when you create a microservices architecture—and learn how to recover if you fall into one

Who Should Read This Book:
This book is for senior engineers, architects, and technical leaders who are moving to microservices and wondering what that means for all the techniques and processes they currently use. It is also for those already using microservices who are struggling with the complexity and want to learn how other people have successfully met some of those challenges. I assume you are familiar with the fundamental concepts of software development and architecture, but I don’t assume you already have experience with microservice architecture.