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
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
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
Definitely approach #1. Having your clients talk to multiple GraphQL services (as in approach #2) entirely defeats the purpose of using GraphQL in the first place, which is to provide a schema over your entire application data to allow fetching it in a single roundtrip. Having a shared nothing architecture might seem reasonable from the … Read more