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)

Testing strategies for microservices

Software industries are now using the microservice-based architecture for every new development. In addition, most companies are moving from monolithic to microservice-based architectures. Consequently, each microservice must be tested before it communicates with other microservices.

As we know, a microservice is an architectural style that develops a single application with a suite of services. These services are independent deployable, have different data storage methods, and can also be used in different languages. They either have a bare minimum of dependencies or zero dependencies with centralized management. These services are built around business capability and can also be deployed by containers. Sometimes, this characteristic of the microservice style creates complexity for testers trying to test a microservice end-to-end.

...