1. Brief your existing/last Project architecture ? 2. Design patterns used in microservice architecture ?(Since my last project was microservices) 3. What is saga pattern? 4. 2 Scenario based question - Data lost scenario of kafka cluster? multiple follow up question on this scenario , also covering how to prevent data duplication ? 5. Manual and auto commit of Kafka consumer? 6. Questions on monitoring and recovery - How to visualize data on Appdynamics visual diaplay ?fault tolarence and recovery approach ?

Question

Accepted Answer

Answering questions related to microservice architecture, design patterns, Kafka cluster data loss prevention, and monitoring/recovery in Appdynamics.

My last project architecture was based on microservices, utilizing design patterns such as Circuit Breaker, Service Registry, and API Gateway.
Saga pattern is used in microservices to manage distributed transactions across multiple services.
In the event of data loss in a Kafka cluster, it is important to have proper replication and backup strategies in place to prevent data duplication.
Kafka consumers can be configured for manual or auto commit, with manual commit providing more control over message processing.
Monitoring and recovery in Appdynamics involves visualizing data through dashboards, implementing fault tolerance mechanisms, and having a robust recovery approach in case of failures.

Popular interview questions of Technical Program Manager

Top HR questions asked in MasterCard Technical Program Manager