Book Image

Hands-On Docker for Microservices with Python

By : Jaime Buelta
Book Image

Hands-On Docker for Microservices with Python

By: Jaime Buelta

Overview of this book

Microservices architecture helps create complex systems with multiple, interconnected services that can be maintained by independent teams working in parallel. This book guides you on how to develop these complex systems with the help of containers. You’ll start by learning to design an efficient strategy for migrating a legacy monolithic system to microservices. You’ll build a RESTful microservice with Python and learn how to encapsulate the code for the services into a container using Docker. While developing the services, you’ll understand how to use tools such as GitHub and Travis CI to ensure continuous delivery (CD) and continuous integration (CI). As the systems become complex and grow in size, you’ll be introduced to Kubernetes and explore how to orchestrate a system of containers while managing multiple services. Next, you’ll configure Kubernetes clusters for production-ready environments and secure them for reliable deployments. In the concluding chapters, you’ll learn how to detect and debug critical problems with the help of logs and metrics. Finally, you’ll discover a variety of strategies for working with multiple teams dealing with different microservices for effective collaboration. By the end of this book, you’ll be able to build production-grade microservices as well as orchestrate a complex system of services using containers.
Table of Contents (19 chapters)
Free Chapter
1
Section 1: Introduction to Microservices
3
Section 2: Designing and Operating a Single Service – Creating a Docker Container
7
Section 3:Working with Multiple Services – Operating the System through Kubernetes
13
Section 4: Production-Ready System – Making It Work in Real-Life Environments

Questions

  1. What are the differences between releasing changes in a microservice architecture system and a monolith?
  2. Why should the released changes be small in a microservice architecture?
  3. How does semantic versioning work?
  4. What are the problems associated with semantic versioning for internal interfaces in a microservice architecture system?
  5. What are the advantages of adding a version endpoint?
  6. How can we fix the dependency problem in this chapter's code?
  7. Which configuration variables should we store in a shared ConfigMap?
  8. Can you describe the advantages and disadvantages of getting all the configuration variables in a single shared ConfigMap?
  9. What's the difference between a Kubernetes ConfigMap and a Kubernetes secret?
  10. How can we change a Kubernetes secret?
  11. Imagine that, based on the configuration, we decided to change the public_key.pub file from a secret to a ConfigMap...