Sidecar pattern in Microservices - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a sidecar container that runs alongside the main application container.

Microservices

containers:
  - name: main-app
    image: myapp:latest
  - name: sidecar
    image: [1]

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

Asidecar-proxy:latest

Bmain-app:latest

Cdatabase:latest

Dcache:latest

Attempts:

3 left

💡 Hint

Common Mistakes

Using the main application image for the sidecar container.

Using unrelated service images like database or cache.

The sidecar container typically runs a proxy or helper service, so the image should be a sidecar proxy image.

2fill in blank

medium

Complete the code to show how the sidecar pattern helps with logging in microservices.

Microservices

main_service_logs -> [1] -> centralized_logging_system

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

Aload_balancer

Bdatabase

Csidecar_container

Dcache

Attempts:

3 left

💡 Hint

Common Mistakes

Using database or cache which are unrelated to log forwarding.

Confusing load balancer with sidecar functionality.

The sidecar container collects logs from the main service and forwards them to a centralized logging system.

3fill in blank

hard

Fix the error in the description of the sidecar pattern usage.

Microservices

The sidecar pattern runs the helper service in a separate [1] from the main application.

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

Aprocess

Bcontainer

Cserver

Ddatabase

Attempts:

3 left

💡 Hint

Common Mistakes

Saying it runs as a separate process instead of container.

Confusing it with running on a separate server.

The sidecar pattern runs the helper service in a separate container, not just a process or server.

4fill in blank

hard

Fill both blanks to complete the sidecar pattern benefits.

Microservices

The sidecar pattern helps with [1] and [2] without changing the main application code.

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

Alogging

Bdatabase

Cmonitoring

Dcaching

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing database or caching which are not typical sidecar responsibilities.

Sidecar pattern is commonly used for logging and monitoring as helper services.

5fill in blank

hard

Fill all three blanks to complete the sidecar pattern example in Kubernetes YAML.

Microservices

containers:
  - name: app
    image: myapp:latest
  - name: [1]
    image: [2]
    ports:
      - containerPort: [3]

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

Asidecar-proxy

Bsidecar-logger

C15000

Dsidecar-proxy:latest

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong container names or images.

Incorrect port numbers.

The sidecar container is named 'sidecar-proxy', uses the 'sidecar-proxy:latest' image, and exposes port 15000.