We deploy microservices in Kubernetes environment.
For providing a solution to a business use-case using microservices,
Is the idea of service registration and service discovery not an anti pattern? where the scenario of starting microservice depends on the availability of other microservice
For example, using API composition, we would need service discovery. We have a usecase in ecommerce, where Front end rest api clients(React or Angular) need to talk to backend(checkout, cart, order, review) services using api composition pattern, to render UI. Not sure, if event based messaging pattern(say using kafka) would be a good option between Front end & Back end services, just to avoid api composition
As mentioned here,
What are microservices?
Microservices - also known as the microservice architecture - is an architectural style that structures an application as a collection of services that are:
Organized around business capabilities
Owned by a small team