Microservice architecture offers a competitive platform based on loosely coupled services that are easy to change, deploy, and scale-out. However, a pure event-driven approach can result in a distributed monolithic architecture that is tightly coupled. This article explores the issues that arise when relying solely on events and the solution of incorporating commands. It highlights the difference between events and commands and their proper usage in a well-balanced architecture. An example of incorporating commands in a microservice at NA-KD eCommerce is provided as a use case. With a proper balance of events and commands, an event-driven microservice architecture can deliver high-performance, scalable, and adaptable software that is perfect in today’s fast-paced environment.
