Microservice Architecture · interview question
When designing a microservices architecture, what is a potential drawback of the 'database-per-service' rule?
Multiple choiceHardchapter-18-curatedpremiummicroservice-architecturebounded-contexts
Answer and explanation
Correct answer
D. It can lead to data duplication.
Why
While 'database-per-service' promotes service independence, it can lead to data duplication and inconsistencies, as data needs to be synchronized or replicated across different services.
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?