Based on what I understand, a good way to resolve it is by using the OAuth 2 protocol (you can find a little more information about it on http://oauth.net/2/) When your user logs into your application they will get a token and with this token they will be able to send to other services to … Read more
An ExternalName service is a special case of service that does not have selectors and uses DNS names instead. You can find out more about ExternalName service from the official Kubernetes documentation: When you want to access a service from a different namespace, your yaml could, for example, look like this: kind: Service apiVersion: v1 … Read more
The evils of too much coupling between services are far worse than the problems caused by code duplication The author is very unspecific when he uses the generic word “coupling”. I would agree with certain types of coupling being a strict no-no (like sharing databases or using internal interfaces). However the use of common libraries … Read more
How can I setup something like eureka.client.serviceUri? You have to have a Kubernetes service on top of the eureka pods/deployments which then will provide you a referable IP address and port number. And then use that referable address to look up the Eureka service, instead of “8761”. To address further question about HA configuration of … Read more
This is a very important question because a few people get lured by all the buzz around microservices, and there are tradeoffs to consider. So, what are the benefits and challenges of microservices (when compared with the monolithic model)? Benefits Deployability: more agility to roll out new versions of a service due to shorter build+test+deploy … Read more
The Book Building Microservices describes in detail the styles mentioned by @RogerAlsing in his answer. On page 43 under Orchestration vs Choreography the book says: As we start to model more and more complex logic, we have to deal with the problem of managing business processes that stretch across the boundary of individual services. And … Read more
What doesn’t make sense: distributed transactions with REST services. REST services by definition are stateless, so they should not be participants in a transactional boundary that spans more than one service. Your user registration use case scenario makes sense, but the design with REST microservices to create User and Wallet data is not good. What … Read more