[Solved] Your microservices team must choose between REST and gRPC for inter-service... To document this decision in an ADR, which structure best captures the rationale, alternatives, and trade-offs? | Microservices

Microservices - Real-World Architecture Case Studies

Your microservices team must choose between REST and gRPC for inter-service communication. To document this decision in an ADR, which structure best captures the rationale, alternatives, and trade-offs?

ATitle, Status, Context, Decision, Alternatives, Consequences

BTitle, Status, Decision, Implementation Details, Testing Plan

CTitle, Context, Decision, Deployment Strategy, Rollback Plan

DTitle, Status, Context, Decision, Performance Metrics

Step-by-Step Solution

Solution:

Step 1: Identify key ADR sections
Standard ADRs include Context, Decision, Consequences, and sometimes Alternatives.
Step 2: Evaluate options
Title, Status, Context, Decision, Alternatives, Consequences includes Alternatives and Consequences, which help document pros, cons, and impact.
Step 3: Exclude irrelevant sections
Implementation, Testing, Deployment, and Performance Metrics are not typical ADR sections.
Final Answer:
Title, Status, Context, Decision, Alternatives, Consequences -> Option A
Quick Check:
Alternatives and Consequences are key ADR parts [OK]

Quick Trick: Include Alternatives and Consequences in ADRs for clear decisions [OK]

Common Mistakes:

Omitting Alternatives section
Including implementation details in ADR
Confusing ADR with project plans

Master "Real-World Architecture Case Studies" in Microservices

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Arch Try Challenge Design Recall Scale

More Microservices Quizzes

To document this decision in an ADR, which structure best captures the rationale, alternatives, and trade-offs?

Step 1: Identify key ADR sections

Step 2: Evaluate options

Step 3: Exclude irrelevant sections

Final Answer:

Quick Check:

Want More Practice?