Testing BookInfo app with Circuit Breaker based policy
The third and last test in the Service Mesh, is using a Circuit Breaker based pattern. It further protects our microservices in case of certain conditions occur, such as preventing that an unexpected number of requests overflow and affect the microservices in the service mesh.
We might decide to throttle or simply reject new incoming requests when a number of current incoming http requests reaches certain threshold.
For demonstration purposes, we are going to set rules to allow a maximum of 1 request at a time. If more than 1 request comes in, we will prevent it from entering the mesh.
Welcome to the Cloud Native App Dev Series. We built and constantly maintain this space to help others get up to speed with Cloud Native App Dev technologies and discover the power of Autonomous Cloud Services.
Containers 101: Learn how to containerise and ship your applications to Kubernetes using Docker
Kubernetes 101: Get familiar with Kubernetes architecture and components.
*Special thanks to Cameron Senese for being a great mentor and a Cloud warrior, helping us demystify the exciting world of Kubernetes and Microservices… As we keep demystifying technologies and patterns, we are going to keep adding interesting topics, so you better stay tuned!
In this Lab, we will show how to manage a more complex Microservices-based application based on an E-Commerce Socks-shop App (also see here). Similarly, as with the Simpler Cheeses App, we are going to use Weave Scope to gather real-time insight into this more complex application.
This is an e-commerce application that sells socks on web. However, we chose this application because it is not any different to any modern Application. That is, it is based on multiple microservices, where each one use different technologies as programming languages/frameworks, as well as persistent back stores or databases.
In this Lab, we will show how to deploy microservices-based Applications into Kubernetes cluster. Then we are going to use an Open Source framework called Weave Scope, to gather in real-time runtime insight into it. We will finish by learning a few tricks to easily manage your microservices.
The Application that we are going to deploy is based on “Cheeses“. It is made of 3 microservices (3 types of cheeses) that when invoked via an API, they simply return their own name (i.e. cheddar, stilton, or wensleydale).
In this blog, you will get familiar with the Kubernetes Cluster UI Dashboard and with the various components that are pre-deployed in your sandbox environment.
Kubernetes Dashboard UI is a web-based interface that lets you visually see all the different components of the Kubernetes cluster, as well as to deploy and manage Applications via Containers running on Pods. It also provides ability to overview the health of the various components and troubleshoot your various components specifications.
The Kubernetes Dashboard UI comes with a vertical menu. Let’s review the main sections in this menu:
This Kubernetes workshop aims to get you familiar, via experimentation, across the various components that make up the important aspects of Kubernetes, as a platform to host and manage the life-cycle of Microservices.
Kubernetes is an open-source platform for automating deployment, scaling, and operations of application containers across clusters of hosts, providing container-centric infrastructure
Kubernetes provides a container-centric management environnement. It orchestrates computing, networking, and storage infrastructure on behalf of user workloads. This provides much of the simplicity of Platform as a Service (PaaS) with the flexibility of Infrastructure as a Service (IaaS), and enables portability across infrastructure providers.