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

Chapter 10

  1. What is the observability of a system?

It's the capacity of a system. It lets you know what its internal state is.

  1. What are the different severity levels that are available in logs by default?

In order of increasing severity, the different severity levels are DEBUG, INFO, WARNING, ERROR, and CRITICAL.

  1. What are metrics used for?

Metrics allow you to find out the aggregated statuses of the events that are occurring on the system and allow you to understand the general state of the system.

  1. Why do you need to add a request ID to the logs?

You need to add a request ID to the logs so that you can group all of the logs that correspond to the same request.

  1. What kinds of metrics are available in Prometheus?

Counters, which count a particular event; gauges, which keep track of a value that can go either up or down; and histograms (or summaries), which track events...