Using HTTP as a means of communication between services, introduces tight coupling as each service needs to know about the existence of the other. Event sourcing solves the coupling problem as each service is unaware of any other. It just listens on events of interest, processes them and produces new events. At least, in theory. Even though you have event sourcing, in some cases you cannot avoid asking other service for a piece of information.
This talk is about how to design your services to support the query communication pattern. There are several approaches how this can be solved, none of them is almighty, each has its pros and cons. The decision should be made carefully.
Vladimir Vajda works as Data Engineer at SmartCat. He started as Java developer but got interested in distributed and data intensive systems and system architecture. Loves great argument, a good book, good beer and tasty food. He usually spends his spare time with his family or thinkering and playing with some new technology or project.