Localized Testing and Debugging of Microservices
From the previous chapters, we understand that the MTAEDA application sample code currently contains a mix of runtime components: two self-coded microservices (Producer and Consumer), and three supporting services (Zookeeper, Kafka, and Kafkadrop). We saw that the Kafka service is configured with a level of redundancy. However, to leverage the full performance potential of EDA, we must be able to scale all the services by adding more instances in an orchestrated pattern.
This provides us with a configuration management challenge that is common across all modern application development practices today – not just for EDA:
- How do we develop and test efficiently with so many components to manage?
- Can we provide multiple developers and teams with a consistent environment?
- Will higher environments be reliably consistent with the development environment?
This chapter intends to walk through adding the configurations...
