The designer of the NGINX Microservices Reference Architecture describes and compares its three models: Proxy Model, Router Mesh Model, and Fabric Model.
Microservices are currently getting a lot of attention. This blog post is the first in a 7-part series about designing, building, & deploying microservices.
Migrating your monolithic application to microservices can be accomplished gradually, with clear benefits at each step.
Learn how an event-driven microservices architecture solves the distributed data management challenges caused by separate per-service datastores.
Explore the advantages and drawbacks of deploying microservices server instances on physical hosts or VMs, in containers, or statelessly.
Learn the pros and cons of the different technologies you can choose for inter-process communication in your microservices-based application
Explore the service discovery within a microservices architecture, including client-side and server-side discovery patterns, the service registry, & more.
Learn why and how to build microservices using API gateways for communication between clients and applications.
The NGINX Microservices Reference Architecture includes three models for development – the Proxy Model, the Router Mesh Model, and the Fabric Model.
Explore the benefits of implementing NGINX Plus as a reverse proxy server in the Proxy Model of the Microservices Reference Architecture from NGINX