Book Image

Hands-On Microservices with Kubernetes

By : Gigi Sayfan
Book Image

Hands-On Microservices with Kubernetes

By: Gigi Sayfan

Overview of this book

Kubernetes is among the most popular open source platforms for automating the deployment, scaling, and operations of application containers across clusters of hosts, providing a container-centric infrastructure. Hands-On Microservices with Kubernetes starts by providing you with in-depth insights into the synergy between Kubernetes and microservices. You will learn how to use Delinkcious, which will serve as a live lab throughout the book to help you understand microservices and Kubernetes concepts in the context of a real-world application. Next, you will get up to speed with setting up a CI/CD pipeline and configuring microservices using Kubernetes ConfigMaps. As you cover later chapters, you will gain hands-on experience in securing microservices and implementing REST, gRPC APIs, and a Delinkcious data store. In addition to this, you’ll explore the Nuclio project, run a serverless task on Kubernetes, and manage and implement data-intensive tests. Toward the concluding chapters, you’ll deploy microservices on Kubernetes and learn to maintain a well-monitored system. Finally, you’ll discover the importance of service meshes and how to incorporate Istio into the Delinkcious cluster. By the end of this book, you’ll have gained the skills you need to implement microservices on Kubernetes with the help of effective tools and best practices.
Table of Contents (16 chapters)

Self-healing with Kubernetes

Self-healing is a very important property of large-scale systems made up of a myriad of physical and virtual components. Microservice-based systems running on large Kubernetes clusters are a prime example. Components can fail in multiple ways. The premise of self-healing is that the overall system will not fail and will be able to automatically heal itself, even if this causes it to operate in a reduced capacity temporarily.

The building blocks of such reliable systems are as follows:

  • Redundancy
  • Observability
  • Auto-recovery

The basic premise is that every component might fail machines crash, disks get corrupted, network connections drop, configuration may get out of sync, new software releases have bugs, third-party services have outages, and so on. Redundancy means there are no single point of failures (SPOFs). You can run multiple replicas...