Accept cookies for analytics, social media, and advertising, or learn more and adjust your preferences. These cookies are on by default for visitors outside the UK and EEA. Privacy Notice.
What a microservice is, when and why it makes sense to adopt microservices
How to implement an API gateway to route traffic to microservices
Pros and cons of different microservices patterns for design and deployment
Different strategies for refactoring a monolith to microservices
Microservices architecture is the new standard for building applications. Converting your apps to a microservices approach makes them more flexible, more stable, and far faster and easier to update. However, it’s not always obvious how to transition traditional, monolithic applications to microservices. Microservices examples and frank discussions of architectural choices are few and far between.
The seven‑part series on microservices development published in the NGINX blog provided many of the answers. It also served to introduce the robust microservices framework contained in the NGINX Microservices Reference Architecture. Now, we have created an ebook that combines these blog posts with information on how to use NGINX Plus in building microservices apps.
Chris Richardson is the founder of the original CloudFoundry.com, an early Java PaaS (Platform as a Service) for Amazon EC2, and leads the microservices.io blog, with many microservices examples. He now consults with organizations to improve how they develop and deploy applications.
Floyd Earl Smith has been involved in application development since the launch of the Macintosh and has written more than 20 books on hardware and software topics. He now writes for the NGINX blog, including contributing to blog posts and webinars about the NGINX Microservices Reference Architecture, a breakthrough microservices framework.
