[Solved] Given this ADR excerpt:Title: Use REST for service communication Status: Accepted Context: Need simple, stateless communication Decision: Use REST over HTTP Consequences:... | Microservices

Microservices - Real-World Architecture Case Studies

Given this ADR excerpt:

Title: Use REST for service communication
Status: Accepted
Context: Need simple, stateless communication
Decision: Use REST over HTTP
Consequences: Easier integration but higher latency

What is the main consequence documented here?

AREST requires stateful connections for speed

BREST causes stateless communication to fail

CREST reduces integration complexity and latency

DREST leads to easier integration but higher latency

Step-by-Step Solution

Solution:

Step 1: Read the Consequences section carefully
The consequence states "Easier integration but higher latency".
Step 2: Match the consequence with options
REST leads to easier integration but higher latency matches exactly; others contradict the text.
Final Answer:
REST leads to easier integration but higher latency -> Option D
Quick Check:
Consequence = Easier integration, higher latency [OK]

Quick Trick: Focus on Consequences section for effects [OK]

Common Mistakes:

Ignoring the 'higher latency' part
Assuming REST reduces latency
Confusing stateless with stateful

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

Given this ADR excerpt:

Step 1: Read the Consequences section carefully

Step 2: Match the consequence with options

Final Answer:

Quick Check:

Want More Practice?