Distributed Resilience · interview question
Which of the following best describes the 'Database-per-Service' pattern in a microservices architecture?
Multiple choiceHardchapter-18-curatedpremiumdistributed-resilienceexponential-backoff-retries
Answer and explanation
Correct answer
A. Each service has its own database, ensuring loose coupling and service autonomy
Why
The 'Database-per-Service' pattern ensures each microservice has its own database, enabling loose coupling, service autonomy, and scalability, while preventing direct dependencies between services.
Test yourself on Distributed Resilience
A free test with instant, explained results. No account needed.
More Distributed Resilience questions
- Which problem might occur if correlation IDs are not propagated consistently across all services in a distributed…
- How would you explain a common approach to implementing retries in a microservices-based Java application in an…
- What could be a consequence of setting a very high threshold for failure in a circuit breaker?
- How would you explain a potential risk when not implementing exponential backoff during retries in microservices in an…
- How does distributed tracing assist in the performance optimization of a microservice architecture?
- In a distributed system, how does injecting a unique correlation ID at the API edge router help in monitoring?