Part I. Context
Before we look at how to set up an organization to make a success of microservices, and how to change the way you think about building and operating software, let’s set the context.
We’ll start, in Chapter 1, with a full definition of the microservices architectural style, including its benefits and challenges. This chapter will also cover the technologies and processes that tend to go along with microservices, and why they have enabled this style of architecture. I will also look at some of the forerunners and alternatives to microservices. This chapter provides a foundation for the rest of the book, and those already familiar with microservices can go straight to Chapter 2, although it may be worth reading it anyway to make sure we have a shared perspective on what microservices really are.
Chapter 2 looks at what high-performing software delivery looks like, and considers where microservices help and where they make things more difficult. This chapter also introduces many of the concepts we’ll dig into in the remainder of the book. You can use it to get a quick overview, or to help you skip straight to the aspects of microservices that you are grappling with.
Microservices can be a very effective architecture, but they are not the only approach. In Chapter 3, I’ll help you assess whether microservices are the right approach for you.
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access