Book Image

Hands-On Microservices ??? Monitoring and Testing

By : Dinesh Rajput
5 (1)
Book Image

Hands-On Microservices ??? Monitoring and Testing

5 (1)
By: Dinesh Rajput

Overview of this book

Microservices are the latest "right" way of developing web applications. Microservices architecture has been gaining momentum over the past few years, but once you've started down the microservices path, you need to test and optimize the services. This book focuses on exploring various testing, monitoring, and optimization techniques for microservices. The book starts with the evolution of software architecture style, from monolithic to virtualized, to microservices architecture. Then you will explore methods to deploy microservices and various implementation patterns. With the help of a real-world example, you will understand how external APIs help product developers to focus on core competencies. After that, you will learn testing techniques, such as Unit Testing, Integration Testing, Functional Testing, and Load Testing. Next, you will explore performance testing tools, such as JMeter, and Gatling. Then, we deep dive into monitoring techniques and learn performance benchmarking of the various architectural components. For this, you will explore monitoring tools such as Appdynamics, Dynatrace, AWS CloudWatch, and Nagios. Finally, you will learn to identify, address, and report various performance issues related to microservices.
Table of Contents (11 chapters)

Using an API gateway

As a best practice, a client must not have information about your microservice hosts and ports. All clients must be aware of the single entry point to all microservices. In this case, we have to implement an API gateway that provides a single entry point for clients. This is a much better approach than direct client-to-service communication.

An API gateway is an edge server that provides services to a client that is similar to the Facade pattern from object-oriented design. The API gateway hides the diversity of protocols from multiple background microservices and instead provides a common API for each client and microservice. An API gateway is responsible for request routing, composition, and protocol translation. They may also have other functionalities, such as authentication, monitoring, load balancing, caching, request shaping and management, and static...