Home > front end >  Microservices Architecture Best Practice [closed]
Microservices Architecture Best Practice [closed]

Time:10-02

I will be appritiated if anyone answer to below quesions.

  1. How a system will be designed with hundreds of services if each and every service has to be independent with a dedicated port as per microservices architecture? i mean is it a good practice to open hundreds of ports on OS for example?

  2. How to expose all the services with a single port to customer?

  3. Is microservice a perfect solution in such a systems?

Best Regards.

CodePudding user response:

  1. For security reasons microservices are hosted in private vpc, i.e. the nodes (where the microservices are run) does not have public ip. And the only way to get access to them is via a gateway api (see below). Also "each and every services has to be independent" should be in the means of domain link1 link2.

  2. To expose services use the API gateway pattern: "a service that provides a single-entry point for certain groups of microservices" link1 link2. Note that api gateway is for a group of microservices, i.e. there may be several gateways for different groups of services (one for public api, one for mobile api, etc).

  3. Only you can answer this question because only you knows what problem you try to solve. Before deciding I recommend to read about MonolithFirst approach

CodePudding user response:

Micro services architecture is somehow the next generation of ESB products but in this case due to the high number of services,I am not sure if it is a solution!

  • Related