Microservices Core Architectural Principles 3

Question 1

Which pattern decomposes a monolith based on distinct business sub-domains?

Accepted Answer

Decompose by business capability

Answer

Decomposition by business capability aligns each service with a discrete business function.

Question 2

In microservices, what is the preferred way for services to communicate to maximize loose coupling?

Accepted Answer

Well-defined APIs and asynchronous messaging

Answer

Loose coupling is achieved through explicit APIs and asynchronous, event-driven messaging.

Question 3

What does the principle of 'design for failure' imply for microservices?

Accepted Answer

Build resilience because failures are inevitable

Answer

Distributed systems must assume failures will happen and build in resilience mechanisms.

Question 4

Which fallacy of distributed computing warns architects most directly when designing service calls?

Accepted Answer

The network is reliable

Answer

'The network is reliable' is a classic fallacy that microservice designs must explicitly guard against.

Question 5

What is the main benefit of organizing teams around services rather than technical layers?

Accepted Answer

It enables cross-functional teams that own a service end-to-end

Answer

Conway's Law favors cross-functional teams owning services end-to-end, improving autonomy and delivery speed.

Microservices Practice Test