Why inter-service communication defines architecture in Microservices - Architecture Impact

System Overview - Why inter-service communication defines architecture

This system shows how microservices communicate with each other to fulfill user requests. The way services talk defines the system's structure, performance, and reliability. Key needs include clear communication paths, fault tolerance, and scalability.

Architecture Diagram

User
  |
  v
Load Balancer
  |
  v
API Gateway
  |
  +---------------------+
  |                     |
  v                     v
Service A <-----> Service B
  |                     |
  v                     v
Database A           Database B
  ^                     ^
  |                     |
Cache A               Cache B

Components

User

user

Initiates requests to the system

Load Balancer

load_balancer

Distributes incoming requests evenly to API Gateway instances

API Gateway

api_gateway

Entry point that routes requests to appropriate microservices

Service A

service

Handles specific business logic and communicates with Service B

Service B

service

Handles another business domain and collaborates with Service A

Database A

database

Stores data related to Service A

Database B

database

Stores data related to Service B

Cache A

cache

Speeds up data access for Service A

Cache B

cache

Speeds up data access for Service B

Request Flow - 16 Hops

User → Load Balancer

Load Balancer → API Gateway

API Gateway → Service A

Service A → Cache A

Cache A → Service A

Service A → Database A

Database A → Service A

Service A → Service B

Service B → Cache B

Cache B → Service B

Service B → Database B

Database B → Service B

Service B → Service A

Service A → API Gateway

API Gateway → Load Balancer

Load Balancer → User

Failure Scenario

Component Fails:Service B

Impact:Service A cannot get data from Service B, causing partial failure or delay in response.

Mitigation:Implement retries, fallback responses, or circuit breaker patterns to handle Service B failure gracefully.

Architecture Quiz - 3 Questions

Which component first distributes user requests to the system?

A Load Balancer

B API Gateway

C Service A

D Cache A

Design Principle

Inter-service communication shapes the system's architecture by defining how services depend on each other. Clear communication paths enable scalability and fault tolerance, while poor design can cause delays or failures. Using caches, databases, and gateways properly ensures efficient and reliable data flow.

Practice

1. Which of the following best explains why inter-service communication is crucial in microservices architecture?

easy

A. It only affects the user interface design of the application.

B. It determines how services coordinate and impacts system performance and reliability.

C. It is used to store data permanently in the database.

D. It defines the programming language used for each service.

Solution

1. Step 1: Understand the role of inter-service communication

   Inter-service communication allows different microservices to work together by exchanging data and requests.

2. Step 2: Identify its impact on system qualities

   This communication affects how fast and reliable the overall system is, as services depend on each other to complete tasks.

3. Final Answer:

   It determines how services coordinate and impacts system performance and reliability. -> Option B

4. Quick Check:

   Communication defines coordination and performance = B [OK]

Hint: Focus on coordination and system impact for communication [OK]

Common Mistakes:

• Confusing communication with UI design
• Thinking communication stores data permanently
• Believing communication defines programming language

2. Which syntax correctly represents asynchronous communication between two microservices using message queues?

easy

A. serviceA.publishToQueue('taskQueue', message)

B. serviceA.sendRequest(serviceB)

C. serviceA.call(serviceB).wait()

D. serviceA.invoke(serviceB).sync()

Solution

1. Step 1: Identify asynchronous communication syntax

   Asynchronous communication uses message queues where a service publishes messages without waiting for immediate response.

2. Step 2: Match syntax to asynchronous pattern

   publishToQueue sends a message to a queue, fitting asynchronous style; other options imply direct or synchronous calls.

3. Final Answer:

   <code>serviceA.publishToQueue('taskQueue', message)</code> -> Option A

4. Quick Check:

   Message queue publish = A [OK]

Hint: Look for 'publish' or 'queue' to spot async communication [OK]

Common Mistakes:

• Choosing direct method calls as async
• Confusing synchronous wait with async
• Ignoring message queue terminology

3. Given the following code snippet for synchronous communication, what will be the output if serviceB.process() takes 3 seconds to respond?

response = serviceA.call(serviceB.process)
print('Response received')

medium

A. Response received (printed immediately)

B. Response received printed twice

C. No output due to error

D. Response received (printed after 3 seconds)

Solution

1. Step 1: Understand synchronous call behavior

   Synchronous calls wait for the called service to finish before continuing execution.

2. Step 2: Analyze the code flow

   Since serviceB.process() takes 3 seconds, print waits and executes after the response arrives.

3. Final Answer:

   Response received (printed after 3 seconds) -> Option D

4. Quick Check:

   Synchronous call delays output = D [OK]

Hint: Synchronous means wait before next step [OK]

Common Mistakes:

• Assuming immediate print without wait
• Thinking output prints twice
• Confusing synchronous with asynchronous

4. Identify the error in this asynchronous communication example using a message queue:

serviceA.publish('taskQueue', message)
serviceB.process()
serviceB.consume('taskQueue')

medium

A. serviceB.consume should be called before process to receive messages

B. serviceA.publish should wait for serviceB.process to finish

C. serviceB.process() should be called after consume

D. No error; the code is correct

Solution

1. Step 1: Understand message consumption order

   To process messages, the consumer must subscribe or consume from the queue before processing.

2. Step 2: Identify incorrect sequence

   Calling serviceB.process() before consume means no messages are received yet, causing a logic error.

3. Final Answer:

   serviceB.consume should be called before process to receive messages -> Option A

4. Quick Check:

   Consume before processing = C [OK]

Hint: Consume messages before processing them [OK]

Common Mistakes:

• Calling process before consuming messages
• Expecting publish to wait for processing
• Thinking code order does not matter

5. You are designing a microservices system where Service A must send a request to Service B and continue working without waiting for a response. Which communication pattern should you choose to ensure scalability and loose coupling?

hard

A. Direct database polling by Service A

B. Synchronous HTTP request with retries

C. Asynchronous messaging via a message queue

D. Tightly coupled RPC calls with blocking

Solution

1. Step 1: Analyze requirement for non-blocking communication

   Service A must not wait for Service B's response, so asynchronous communication is needed.

2. Step 2: Choose scalable and loosely coupled pattern

   Using a message queue allows Service A to send messages and continue, while Service B processes independently, supporting scalability and loose coupling.

3. Final Answer:

   Asynchronous messaging via a message queue -> Option C

4. Quick Check:

   Async messaging for non-blocking and scalability = A [OK]

Hint: Pick async messaging for non-blocking, scalable design [OK]

Common Mistakes:

• Choosing synchronous calls causing blocking
• Using direct DB polling which is inefficient
• Selecting tightly coupled RPC reducing flexibility