I am looking at the video above. I guess we don't need to add annotation @EnableEurekaClient on client. Only pom.xml changes and application.properties are OK.
Hi. It will be helpful if u create one video on how to call microservices with dynamic routing covering api gateway and service discovery. I am just thinking what should be the endpoint url when calling service 1 to service2 if there r multiple instance of microservices
Yes but this breaks the single responsibility principle, for higher levels of fault tolerance and redundancy you should make these two different services in a production environment. This allows them to scale independently and fail independently (as you can implement circuit breakers into the gateway to provide more resilience in production :D).
very simple explanation... Many thanks Hero
Thanks 🙌🤩
very simple and understanding ... keep it up
Thank you so much
Thank you so much. it helped me a lot. :)
Welcome
Very good! Perfect for being so minimal!
Thanks ☺️
Great explanation ❤
Thanks
I am looking at the video above. I guess we don't need to add annotation @EnableEurekaClient on client. Only pom.xml changes and application.properties are OK.
Hi. It will be helpful if u create one video on how to call microservices with dynamic routing covering api gateway and service discovery.
I am just thinking what should be the endpoint url when calling service 1 to service2 if there r multiple instance of microservices
I will create video on that soon , thanks
Thanks nice for the demo
THANKSSSSSSSS
Welcome 👍
Thank you sir
Welcome ☺️
is there a way to dynamically add routing in the API Gateway, instead of defining the routes in application.yml?
I will do video on this
it will be better if you explain each properties you have used
Sure I will try it update
Nice 👍
Thanks
spring boot 3 version. I am unable to import @EnableEurkaClient
No need to add @EnableEurekClient in sp 3. Just run
thank u
Welcome ☺️
Can we create service discovery and gateway service as single application
Ok sure
Yes but this breaks the single responsibility principle, for higher levels of fault tolerance and redundancy you should make these two different services in a production environment.
This allows them to scale independently and fail independently (as you can implement circuit breakers into the gateway to provide more resilience in production :D).
Basically, it's an anti-pattern for Microservice development - every service should do one thing and have it's own independent data source.
api gate way not working please check
Does this work for springboot 3.1.9?
Nvm it worked Thanks alot!!
Thanks