12 Pathways to scalability

 

This chapter covers

  • Scaling microservices to bigger development teams
  • Scaling microservices to meet growing demand
  • Mitigating problems caused by changes
  • Understanding basic security concerns
  • Converting a monolith to microservices
  • Spectrum of possibilities and hybrid approach
  • Building with microservices on a budget

We’ve spent the whole book working toward a production microservices application, so where to now? It’s time to see what microservices can offer us in the future.

Throughout this book, we’ve taken many shortcuts that helped us get started quickly and cheaply with microservices. These shortcuts make it simpler to learn microservices and to bootstrap our fledgling application. Even though FlixTube is a simple application built with a relatively simple process, we’re still using microservices, and this is an architecture that provides us many pathways to future scalability.

In this chapter, we discuss how to manage a growing microservices application. How do we scale up to a bigger development team? How do we scale up to meet the demands of a growing customer base? We also need to talk about basic security concerns and how they relate to microservices. Then, we’ll briefly touch on what it takes to convert an existing monolith to microservices.

12.1 Our future is scalable

12.2 Scaling the development process

12.2.1 Multiple teams

12.2.2 Independent code repositories

12.2.3 Splitting the code repository

12.2.4 The meta-repo

12.2.5 Creating multiple environments

12.2.6 Production workflow

12.3.7 Don’t scale too early