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

How to build an enterprise platform with microservices, NATS, and the integration platform

Even though we've discussed multiple layers of the API-driven enterprise platform approach, not all these layers are used in all practical scenarios. Depending on the complexity of the application, different layers are introduced. For a simple application such as our OPD application, we don't need all four layers that we discussed in the previous section. The following diagram depicts how our OPD application fits into the API-driven approach we discussed previously:

Figure 9.4 – The OPD application with the integration platform

In the preceding diagram, we are implementing our business logic as microservices and using NATS to communicate within these services. In addition to that, we are using an integration services layer to implement certain functionalities that involve interacting with more than one service or modifying the responses that are coming...