Microservices maturity model - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to identify the first maturity level in microservices.

Microservices

The first level of microservices maturity is [1].

Drag options to blanks, or click blank then click option'

AIndependent services

BSingle service

CMonolith

DService mesh

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing monolith with independent services.

The first maturity level is the monolith, where the application is a single unit before splitting into microservices.

2fill in blank

medium

Complete the code to name the maturity level where services are loosely coupled and communicate via APIs.

Microservices

At the [1] level, microservices communicate through APIs and are loosely coupled.

Drag options to blanks, or click blank then click option'

AEvent-driven

BService mesh

CMonolith

DAPI-driven

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing event-driven with API-driven communication.

The API-driven level means services interact through well-defined APIs, enabling loose coupling.

3fill in blank

hard

Fix the error in naming the maturity level where services have automated deployment and monitoring.

Microservices

The [1] level includes automated deployment and monitoring of microservices.

Drag options to blanks, or click blank then click option'

AContinuous delivery

BManual deployment

CMonolith

DAPI-driven

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing manual deployment with continuous delivery.

Continuous delivery level means services are deployed automatically with monitoring in place.

4fill in blank

hard

Fill both blanks to describe the maturity level where services use {{BLANK_1}} for communication and {{BLANK_2}} for resilience.

Microservices

At this level, microservices use [1] for communication and [2] to handle failures gracefully.

Drag options to blanks, or click blank then click option'

Aevent-driven messaging

Bsynchronous REST calls

Ccircuit breakers

Dmanual retries

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing synchronous calls or manual retries for resilience.

Event-driven messaging enables asynchronous communication, and circuit breakers improve resilience by preventing cascading failures.

5fill in blank

hard

Fill all three blanks to complete the description of the highest maturity level involving {{BLANK_1}}, {{BLANK_2}}, and {{BLANK_3}}.

Microservices

The highest maturity level includes [1] for service discovery, [2] for security, and [3] for observability.

Drag options to blanks, or click blank then click option'

Aservice mesh

Bzero-trust security

Cdistributed tracing

Dmonolithic architecture

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing monolithic architecture with advanced microservices features.

Service mesh manages service discovery, zero-trust security ensures strict access control, and distributed tracing provides observability across services.

Practice

1. What is the primary focus of the first level in the Microservices maturity model?

easy

A. Implementing service discovery

B. Adding automated deployment pipelines

C. Breaking a monolith into independent services

D. Ensuring fault tolerance and resilience

Solution

1. Step 1: Understand the initial maturity level goal

   The first level focuses on decomposing a large monolithic application into smaller, independent microservices.

2. Step 2: Identify what is NOT part of the first level

   Service discovery, automation, and resilience come in later levels, not the first.

3. Final Answer:

   Breaking a monolith into independent services -> Option C

4. Quick Check:

   Level 1 = Decomposition [OK]

Hint: First level means splitting monolith, not automation or resilience [OK]

Common Mistakes:

• Confusing service discovery as first step
• Thinking automation is in the first level
• Assuming resilience is the initial focus

2. Which of the following is the correct syntax to describe the second level in the Microservices maturity model?

easy

A. Services register and discover each other dynamically

B. Services are deployed manually without automation

C. Services communicate synchronously without discovery

D. Services handle failures with retries and circuit breakers

Solution

1. Step 1: Recall the second level feature

   The second level introduces dynamic service registration and discovery to enable services to find each other.

2. Step 2: Eliminate incorrect options

   Synchronous communication without discovery is level 1; manual deployment is level 2 or earlier; failure handling is a later level.

3. Final Answer:

   Services register and discover each other dynamically -> Option A

4. Quick Check:

   Level 2 = Service discovery [OK]

Hint: Level 2 means dynamic discovery, not manual or failure handling [OK]

Common Mistakes:

• Mixing synchronous communication with discovery
• Confusing automation with discovery
• Assuming failure handling is level 2

3. Given a microservices system at maturity level 3, which of the following behaviors would you expect when a service fails?

medium

A. The service automatically retries and uses circuit breakers

B. The system crashes because there is no failure handling

C. Services communicate only via direct IP addresses

D. Deployment is done manually without pipelines

Solution

1. Step 1: Identify level 3 features

   Level 3 focuses on resilience, including retries and circuit breakers to handle failures gracefully.

2. Step 2: Check other options for mismatch

   System crashing means no resilience (level 1 or 2); direct IP communication is basic; manual deployment is unrelated to failure handling.

3. Final Answer:

   The service automatically retries and uses circuit breakers -> Option A

4. Quick Check:

   Level 3 = Resilience with retries [OK]

Hint: Level 3 means automatic failure handling, not crashes or manual steps [OK]

Common Mistakes:

• Assuming no failure handling at level 3
• Confusing communication methods with failure handling
• Ignoring automation in deployment

4. A team claims their microservices system is at maturity level 4 but they still deploy services manually and have no automated rollback. What is the main issue here?

medium

A. They have no failure handling or retries

B. They are missing automation and continuous delivery features

C. They do not have independent services

D. They lack service discovery mechanisms

Solution

1. Step 1: Understand level 4 requirements

   Level 4 focuses on automation, continuous integration, and continuous delivery including automated rollback.

2. Step 2: Identify missing features in the claim

   Manual deployment and no rollback means automation is missing, which contradicts level 4 maturity.

3. Final Answer:

   They are missing automation and continuous delivery features -> Option B

4. Quick Check:

   Level 4 = Automation & CI/CD [OK]

Hint: Level 4 requires automation; manual deploy means not level 4 [OK]

Common Mistakes:

• Confusing service discovery with automation
• Thinking independent services imply automation
• Ignoring rollback as part of automation

5. A company wants to improve their microservices maturity from level 2 to level 4. Which combination of changes should they prioritize?

hard

A. Focus on database scaling and ignore service communication

B. Break monolith into services, add manual deployment, and use direct IP communication

C. Implement retries and circuit breakers only, without automation or discovery

D. Add dynamic service discovery, implement automated deployment pipelines, and introduce failure handling

Solution

1. Step 1: Identify level 2 and level 4 features

   Level 2 includes dynamic service discovery; level 3 introduces failure handling; level 4 adds automation like deployment pipelines.

2. Step 2: Match changes to maturity levels

   Add dynamic service discovery, implement automated deployment pipelines, and introduce failure handling includes discovery (level 2), failure handling (level 3), and automation (level 4), covering needed improvements.

3. Step 3: Eliminate incorrect options

   Break monolith into services, add manual deployment, and use direct IP communication lacks automation and discovery; Implement retries and circuit breakers only, without automation or discovery misses automation; Focus on database scaling and ignore service communication ignores communication and automation.

4. Final Answer:

   Add dynamic service discovery, implement automated deployment pipelines, and introduce failure handling -> Option D

5. Quick Check:

   Level 2 to 4 = Discovery + Automation + Resilience [OK]

Hint: Level 4 needs automation plus discovery and failure handling [OK]

Common Mistakes:

• Ignoring automation when moving to level 4
• Thinking only retries are enough
• Focusing on unrelated scaling aspects