Book Image

Designing Microservices Platforms with NATS

By : Chanaka Fernando
5 (1)
Book Image

Designing Microservices Platforms with NATS

5 (1)
By: Chanaka Fernando

Overview of this book

Building a scalable microservices platform that caters to business demands is critical to the success of that platform. In a microservices architecture, inter-service communication becomes a bottleneck when the platform scales. This book provides a reference architecture along with a practical example of how to implement it for building microservices-based platforms with NATS as the messaging backbone for inter-service communication. In Designing Microservices Platforms with NATS, you’ll learn how to build a scalable and manageable microservices platform with NATS. The book starts by introducing concepts relating to microservices architecture, inter-service communication, messaging backbones, and the basics of NATS messaging. You’ll be introduced to a reference architecture that uses these concepts to build a scalable microservices platform and guided through its implementation. Later, the book touches on important aspects of platform securing and monitoring with the help of the reference implementation. Finally, the book concludes with a chapter on best practices to follow when integrating with existing platforms and the future direction of microservices architecture and NATS messaging as a whole. By the end of this microservices book, you’ll have developed the skills to design and implement microservices platforms with NATS.
Table of Contents (15 chapters)
1
Section 1: The Basics of Microservices Architecture and NATS
5
Section 2: Building Microservices with NATS
11
Section 3: Best Practices and Future Developments

Defining the solution architecture

Let's put all the knowledge we have gathered so far into a solution architecture so that we can start implementing the microservice-based OPD application. This solution architecture is a simplified version of the reference architecture that we discussed in Chapter 5, Designing a Microservice Architecture with NATS:

Figure 6.5 – Solution architecture for the OPD application

Let's take a deeper look at our solution architecture to understand the components we have used to build the solution.

Clients (Consumers)

Let's start from the top section of the preceding diagram, where we have the Customers or Clients who are accessing the OPD application. We have chosen a simple web application as the client to represent different types of API consumers that can exist in real-world applications. In addition to that, we will discuss how third-party application developers can utilize the overall solution to build...