S90-08 practice question 28 of 35

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

Full set: 100 questions
Answer options
A: Redundant Implementation
B: Stateful Services
C: State Repository
D: None of the above. Correct answer
Correct Answer:
D. None of the above.
Explanation

The design pattern that specifically aims to increase service autonomy by using a replicated database is Service Data Replication. This pattern advocates for providing a service with its own dedicated data store that contains a replicated copy of the required data. This decouples the service from a centralized or shared data source, thereby increasing its operational autonomy and often improving performance. Since the "Service Data Replication" pattern is not listed among options A, B, or C, the correct choice is "None of the above."

Why Incorrect

A. Redundant Implementation: This pattern focuses on providing multiple, redundant implementations of a service's logic to enhance reliability and availability, not on replicating data to increase autonomy.
B. Stateful Services: This is a service design characteristic where a service retains client-specific data across requests. It generally reduces, rather than increases, autonomy and scalability.
C. State Repository: This pattern externalizes state management to a separate component (like a database), enabling services to be more stateless. It does not inherently involve data replication for autonomy.

References

1. Erl, T. (2009). SOA Design Patterns. Prentice Hall.

Service Data Replication Pattern: The purpose of this pattern is explicitly stated as increasing "service autonomy and to minimize performance overhead by providing a service with its own, dedicated data store that is populated with a replicated set of data." (Chapter 17, p. 537). This directly matches the question's description, but is not an available option.

Redundant Implementation Pattern: Described as a pattern to "improve the reliability and availability of a service by providing duplicate implementations for the same service contract." (Chapter 17, p. 525).

State Repository Pattern: Explained as a mechanism to "defer the management of state data to a state repository in order to design stateless services." (Chapter 11, p. 333).

Scroll to Top