Previously, we saw various service registry and discovery options based on service registry and discovery patterns. So, the next question that arises is pretty obvious, which solution to go for? That question is pretty wide and it actually depends on the requirements. Your requirements are most likely to be different than most other companies, so rather than going with the most common solutions, a better approach would be to evaluate your requirements and devise your own strategy based on that. To devise a strategy, the following questions should be properly evaluated:
- Is the system going to be coded in only one language or is there a polyglot environment? Writing the same code in different languages is pretty cumbersome. In this case, Registrator is pretty helpful.
- Is there a legacy system involved? Are both the systems going to run for some time? In this case, self registering solutions can be pretty helpful.
- How simplified is service discovery...