Which pattern aims to increase the autonomy of a service specifically via the use of a replicated database?

Question

Options

• ARedundant Implementation
• BStateful Services
• CState Repository
• DNone of the above.

• A
  6% (3)
• B
  12% (6)
• C
  23% (12)
• D
  60% (31)

Explanation

Option D is correct because the pattern that specifically increases service autonomy through a replicated database is known as Service Data Replication (or a similar name depending on the textbook) - none of the three named options accurately describe this concept.

Redundant Implementation (A) refers to running multiple instances of a service for fault tolerance and availability, not to replicating a database to make a service more independent. Stateful Services (B) simply describes services that maintain internal state between requests - it says nothing about database replication as a mechanism for autonomy. State Repository (C) is about externalizing a service's state into a shared store, which can actually reduce autonomy by creating coupling to a shared data source rather than giving the service its own replicated copy.

Memory tip: Think "RAID vs. replica" - Redundant implementation is like RAID (duplicate instances for resilience), while the autonomy-via-replication pattern gives each service its own copy of the data it needs. If the option doesn't say "replica" or "replication," it probably isn't the answer.

No community discussion yet for this question.