Table of Contents
We have two REST API that is called PlaformService and CommandsService. On our PlatformService we can do all CRUD operations about "Platform" that contains bunch of properties(id, name, publisher...). On the other hand at CommandsService, we have "Commands" that related to "Platform" at PlatformService. One platform object can have multiple commands not vice versa. These REST API's can be functional with their own even they are related to each other. For making this possible we used microservices architecture.
Here with our GET request CommandsService is synchronizing(with Platform Published Event) all existing platforms on PlatformService with its own database. At following screenshot we can see how the flow works on Kubernetes.
