Microservices characteristics - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to identify a key characteristic of microservices.

Microservices

Microservices are designed to be [1] and independently deployable.

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

Atightly integrated

Bloosely coupled

Cmonolithic

Dsingle-threaded

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'monolithic' because it means one big system, which is opposite of microservices.

Microservices are loosely coupled, meaning each service operates independently without tight dependencies.

2fill in blank

medium

Complete the code to describe how microservices communicate.

Microservices

Microservices often communicate using [1] protocols like messaging queues.

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

Aasynchronous

Bsynchronous

Cbatch

Dmanual

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'synchronous' because it implies waiting for responses, which can reduce independence.

Microservices commonly use asynchronous protocols to allow services to work independently and improve scalability.

3fill in blank

hard

Fix the error in the statement about microservices data management.

Microservices

Each microservice should [1] its own database to ensure data isolation.

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

Aignore

Breplicate

Cshare

Down

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'share' because it breaks the independence principle.

Owning its own database allows a microservice to manage data independently, avoiding tight coupling.

4fill in blank

hard

Fill both blanks to complete the microservices design principle.

Microservices

Microservices should be [1] and [2] to allow easy updates and scaling.

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

Aindependent

Bdependent

Cscalable

Dmonolithic

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'dependent' or 'monolithic' which contradict microservices principles.

Microservices are independent and scalable, enabling flexible development and deployment.

5fill in blank

hard

Fill all three blanks to complete the microservices best practices.

Microservices

Use [1] for service discovery, [2] for fault tolerance, and [3] for API communication.

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

Aload balancers

Bcircuit breakers

CREST

Dshared databases

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'shared databases' which breaks service independence.

Load balancers help find services, circuit breakers handle failures, and REST is a common API communication style.

Practice

1. Which of the following is a key characteristic of microservices architecture?

easy

A. Services must be written in the same programming language

B. All services share a single database schema

C. Each service is independently deployable and scalable

D. Microservices require a monolithic deployment

Solution

1. Step 1: Understand microservices independence

   Microservices are designed to be independent units that can be deployed and scaled separately.

2. Step 2: Evaluate options against microservices principles

   Sharing a single database or requiring the same language contradicts microservices flexibility. Monolithic deployment is opposite to microservices.

3. Final Answer:

   Each service is independently deployable and scalable -> Option C

4. Quick Check:

   Independent deployability = C [OK]

Hint: Microservices = independent small services [OK]

Common Mistakes:

• Thinking all services share one database
• Assuming same language is mandatory
• Confusing microservices with monolith

2. Which syntax correctly describes a microservice's responsibility?

easy

A. A microservice focuses on a single business capability

B. A microservice handles multiple unrelated business functions

C. A microservice must handle all user interface logic

D. A microservice should not communicate with other services

Solution

1. Step 1: Identify microservice scope

   Microservices are designed to focus on a single business capability or function.

2. Step 2: Check options for correctness

   Handling multiple unrelated functions or all UI logic is against microservices principles. Communication between services is common and necessary.

3. Final Answer:

   A microservice focuses on a single business capability -> Option A

4. Quick Check:

   Single responsibility = A [OK]

Hint: Microservice = one focused job [OK]

Common Mistakes:

• Thinking microservices do many unrelated tasks
• Believing microservices handle all UI logic
• Ignoring inter-service communication

3. Consider a microservices system where Service A calls Service B, which calls Service C. If Service B fails, what is the expected behavior in a well-designed microservices architecture?

medium

A. Service A receives an error or fallback response quickly

B. All services restart automatically

C. Service C retries the request automatically

D. Service A waits indefinitely for Service B

Solution

1. Step 1: Understand failure handling in microservices

   Microservices use timeouts and fallbacks to avoid waiting indefinitely when a service fails.

2. Step 2: Analyze options for expected behavior

   Waiting indefinitely is bad design. Service C retrying is unrelated to Service B failure. Automatic restart is not immediate failure handling.

3. Final Answer:

   Service A receives an error or fallback response quickly -> Option A

4. Quick Check:

   Timeouts and fallbacks = D [OK]

Hint: Microservices use timeouts, not infinite waits [OK]

Common Mistakes:

• Assuming infinite wait on failure
• Confusing retry logic location
• Expecting automatic restart as immediate fix

4. A developer notices that two microservices share the same database schema directly. What is the main issue with this design?

medium

A. It improves service independence

B. It creates tight coupling between services

C. It reduces data consistency

D. It simplifies service deployment

Solution

1. Step 1: Understand database ownership in microservices

   Each microservice should own its own database to avoid tight coupling.

2. Step 2: Evaluate the impact of shared schema

   Sharing schema creates tight coupling, reducing independence and flexibility. It does not improve independence or simplify deployment.

3. Final Answer:

   It creates tight coupling between services -> Option B

4. Quick Check:

   Shared DB = tight coupling = A [OK]

Hint: Microservices own separate databases [OK]

Common Mistakes:

• Thinking shared DB improves independence
• Assuming shared DB reduces consistency
• Believing shared DB simplifies deployment

5. You are designing a microservices system for an online store. Which approach best supports independent scaling and deployment of the payment and product catalog services?

hard

A. Combine payment and catalog into one service with shared database

B. Deploy payment and catalog as separate modules in the same service

C. Use a single monolithic app for both payment and catalog

D. Separate payment and catalog into distinct services with own databases and APIs

Solution

1. Step 1: Identify microservices best practices for scaling

   Independent services with own databases and APIs allow separate scaling and deployment.

2. Step 2: Compare options for independence and scalability

   Combining services or modules reduces independence. Monolith prevents separate scaling.

3. Final Answer:

   Separate payment and catalog into distinct services with own databases and APIs -> Option D

4. Quick Check:

   Separate services + DBs = B [OK]

Hint: Separate services with own DBs for scaling [OK]

Common Mistakes:

• Combining unrelated services
• Using monolith for microservices goals
• Deploying modules inside one service