For example, your code can read the network locations from a configuration file that is occasionally updated. In a traditional application running on physical hardware, the network locations of service instances are relatively static. In order to make a request, your code needs to know the network location (IP address and port) of a service instance. Let’s imagine that you are writing some code that invokes a service that has a REST API or Thrift API. In this article, we explore the closely related problem of service discovery. The second and third articles in the series describe different aspects of communication within a microservices architecture. The first article introduces the Microservices Architecture pattern and discussed the benefits and drawbacks of using microservices. This is the fourth article in our series about building applications with microservices. Also, please look at the new Microservices Solutions page. You can also download the complete set of articles, plus information about implementing microservices using NGINX Plus, as an ebook – Microservices: From Design to Deployment. Refactoring a Monolith into Microservices.Choosing a Microservices Deployment Strategy.Event-Driven Data Management for Microservices.Service Discovery in a Microservices Architecture (this article).Building Microservices: Inter-Process Communication in a Microservices Architecture.Building Microservices: Using an API Gateway.Editor – This seven‑part series of articles is now complete:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |