Why case studies illustrate practical decisions in Microservices - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a microservice that handles user data.

Microservices

def get_user_data(user_id):
    return database.[1](user_id)

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

Afetch

Bquery

Cdelete

Dupdate

Attempts:

3 left

💡 Hint

Common Mistakes

Using methods that modify or delete data instead of retrieving it.

The method query is used to retrieve data from the database in microservices.

2fill in blank

medium

Complete the code to send a request from one microservice to another.

Microservices

response = service_client.[1]('GET', '/orders')

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

Asend

Bfetch

Cpost

Drequest

Attempts:

3 left

💡 Hint

Common Mistakes

Using methods that are not standard HTTP request methods.

The request method is commonly used to send HTTP requests between microservices.

3fill in blank

hard

Fix the error in the microservice configuration to enable service discovery.

Microservices

service_registry = [1]('http://registry.local')

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

AServiceRegistry

BDiscoveryService

CServiceDiscovery

DRegistryService

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing service discovery with service registry classes.

The ServiceRegistry class is used to register and discover services in microservice architectures.

4fill in blank

hard

Fill both blanks to implement a circuit breaker pattern in microservices.

Microservices

circuit_breaker = CircuitBreaker([1]=5, [2]=60)

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

Afailure_threshold

Btimeout

Cretry_limit

Dreset_timeout

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing retry limits with failure thresholds or timeouts.

The failure_threshold sets how many failures trigger the breaker, and reset_timeout sets how long before retrying.

5fill in blank

hard

Fill all three blanks to create a load balancer configuration for microservices.

Microservices

load_balancer = LoadBalancer(strategy=[1], max_connections=[2], health_check=[3])

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

A'round_robin'

B100

CTrue

D'least_connections'

Attempts:

3 left

💡 Hint

Common Mistakes

Using string values where numbers or booleans are expected.

The least_connections strategy balances load by active connections, 100 limits max connections, and True enables health checks.

Practice

1. Why are case studies important when learning about microservices design?

easy

A. They show real-world decisions and trade-offs made in actual systems.

B. They provide exact code snippets to copy for your projects.

C. They focus only on theoretical concepts without practical examples.

D. They guarantee the best design for every microservice system.

Solution

1. Step 1: Understand the role of case studies

   Case studies present real examples of how systems were designed and the decisions made.

2. Step 2: Identify the benefit of practical decisions

   They reveal trade-offs and challenges faced, helping learners understand practical impacts.

3. Final Answer:

   They show real-world decisions and trade-offs made in actual systems. -> Option A

4. Quick Check:

   Real-world examples = D [OK]

Hint: Case studies show real decisions, not just theory [OK]

Common Mistakes:

• Thinking case studies only provide code
• Assuming case studies are purely theoretical
• Believing case studies guarantee perfect designs

2. Which of the following best describes a practical decision shown in microservices case studies?

easy

A. Writing all microservices in the same programming language regardless of use.

B. Choosing a database technology based on expected load and data type.

C. Ignoring network latency because it rarely affects microservices.

D. Deploying all services on a single server to reduce costs.

Solution

1. Step 1: Identify practical decisions in case studies

   Case studies often show technology choices based on system needs like load and data.

2. Step 2: Evaluate options for realistic decisions

   Choosing a database based on load and data type is a practical, common decision.

3. Final Answer:

   Choosing a database technology based on expected load and data type. -> Option B

4. Quick Check:

   Tech choice by needs = B [OK]

Hint: Practical decisions match system needs, not assumptions [OK]

Common Mistakes:

• Assuming all services must use same language
• Ignoring network latency effects
• Thinking single server deployment is best practice

3. Consider a case study where a microservice was split into two smaller services to improve scalability. What is the most likely practical reason for this decision?

medium

A. To isolate resource-heavy functions for better scaling.

B. To reduce the total number of services in the system.

C. To make deployment more complex and slower.

D. To combine unrelated functionalities into one service.

Solution

1. Step 1: Understand the goal of splitting services

   Splitting services usually aims to isolate parts that need different scaling or resources.

2. Step 2: Analyze options for scalability improvement

   Isolating resource-heavy functions allows scaling only those parts, improving efficiency.

3. Final Answer:

   To isolate resource-heavy functions for better scaling. -> Option A

4. Quick Check:

   Splitting for scaling = A [OK]

Hint: Split services to isolate heavy workloads [OK]

Common Mistakes:

• Thinking splitting reduces total services
• Believing splitting makes deployment slower intentionally
• Combining unrelated functions is not a splitting reason

4. A case study shows a microservice architecture where services communicate synchronously, causing delays. What practical fix does the case study likely suggest?

medium

A. Combine all services into one to avoid communication.

B. Increase the number of synchronous calls to improve reliability.

C. Ignore delays as they do not affect user experience.

D. Switch to asynchronous communication to reduce waiting times.

Solution

1. Step 1: Identify the problem with synchronous communication

   Synchronous calls cause services to wait, increasing delays and reducing performance.

2. Step 2: Find the practical solution from case studies

   Switching to asynchronous communication allows services to work independently, reducing delays.

3. Final Answer:

   Switch to asynchronous communication to reduce waiting times. -> Option D

4. Quick Check:

   Async communication reduces delays = C [OK]

Hint: Async calls reduce wait times in microservices [OK]

Common Mistakes:

• Increasing synchronous calls worsens delays
• Combining services loses microservices benefits
• Ignoring delays harms user experience

5. A case study describes a microservices system that initially used a shared database for all services but later moved to separate databases per service. What practical reasons does the case study illustrate for this change?

hard

A. To force all services to use the same schema.

B. To make data management more complex and slower.

C. To improve service independence and reduce coupling.

D. To reduce the number of databases to manage.

Solution

1. Step 1: Understand the impact of a shared database

   Shared databases create tight coupling, making services dependent on each other's data schemas.

2. Step 2: Analyze benefits of separate databases per service

   Separate databases improve independence, allowing services to evolve without affecting others.

3. Final Answer:

   To improve service independence and reduce coupling. -> Option C

4. Quick Check:

   Separate DBs reduce coupling = A [OK]

Hint: Separate databases increase service independence [OK]

Common Mistakes:

• Thinking separate DBs increase complexity negatively
• Assuming shared DB forces same schema is good
• Believing separate DBs reduce number of databases