Microservice Architecture · interview question
Why is splitting into OrderControllerService, OrderValidationService, and OrderRepositoryService usually a bad microservice design?
Multiple choiceMediumchapter-18-curatedpremiummicroservice-architecturebounded-contexts
Answer and explanation
Correct answer
D. It creates chatty services around technical layers instead of real business ownership
Why
Technical-layer splits often create a distributed monolith. Data and decisions still want to move together, so the system gains network chatter without gaining genuine service independence.
Test yourself on Microservice Architecture
A free test with instant, explained results. No account needed.
More Microservice Architecture questions
- In a microservices architecture using Kafka, what is a typical approach to manage distributed transactions?
- Which of the following best describes the concept of immutable Docker images?
- In the context of microservices, what challenge does Eventual Consistency address?
- How would you explain a key consideration when implementing distributed tracing in a microservices architecture in an…
- How does using Apache Kafka contribute to the resilience of a microservices architecture?
- Which Kubernetes feature is crucial for achieving self-healing in a microservices environment?