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.

Preface

Who this book is for

What this book covers

To get the most out of this book

Free Chapter

Software Architecture Patterns

Software Architecture Patterns

The monolithic architecture pattern

Microservice architecture pattern

Service-oriented architecture (SOA)

SOA versus microservice architecture

Anatomy of Microservice Decomposition Services

Anatomy of Microservice Decomposition Services

Anatomy of a microservice

Decomposition based on business capability

Decomposition on the basis of domain

Microservice chassis to handle cross-cutting concerns

Building microservices

SOAP versus RESTful microservices

Microservices Deployment Patterns

Microservices Deployment Patterns

Microservices deployment

Service deployment platforms

Serverless deployment

Inter-Service Communication

Inter-Service Communication

Approaches to service communication

Event-based communication

Domain-specific protocol

Service Registry and Discovery

Service Registry and Discovery

Technical Requirements

The need for service discovery in microservice architecture

Service discovery patterns

Microservice registry and discovery with Eureka

External API Gateway

External API Gateway

Technical Requirements

Introducing an API gateway

Client-to-microservice communication

Using an API gateway

Building an API gateway

Building an API gateway using Spring Cloud's Netflix Zuul proxy

Testing of Microservices

Testing of Microservices

Technical Requirements

Testing strategies for microservices

Integration testing

Component testing

Contract testing

End-to-end testing

UI/functional testing

Performance Testing of Microservices

Performance Testing of Microservices

Technical Requirements

Performance Monitoring of Microservices

Performance Monitoring of Microservices

Identifying performance counters to test microservices

Performance monitoring tools

Component-level monitoring

Domain-specific monitoring

Dashboards and identifying issues by going through logs

Other Books You May Enjoy

Other Books You May Enjoy

Leave a review - let other readers know what you think

Customer Reviews

5 (1)

5 star

100%

4 star

0

3 star

0

2 star

0

1 star

0

SOAP versus RESTful microservices

SOAP and RESTful microservices have the following differences:

SOAP	RESTful microservices
An XML-based message protocol.	An architectural style.
Uses WSDL for communication between the consumer and the provider.	Use XML or JSON to send and receive data.
Invokes services by calling the RPC method.	Simply call services via the URL path.
The transfer is over HTTP. Also uses other protocols, such as SMTP or FTP.	The transfer is over HTTP only.
SOAP-based reads can't be cached.	RESTful microservice reads can be cached.
SOAP is not very scalable	RESTful microservices are very scalable.
SOAP is more suitable for enterprise systems and high-security systems, such as a banking system.	RESTful microservices are suitable for all types of systems apart from where high security and high reliability is critical...