Anti-corruption layer in Microservices - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define the Anti-corruption Layer interface.

Microservices

class AntiCorruptionLayer {
    public void translate([1] input) {
        // translation logic
    }
}

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

AExternalModel

BInternalModel

CServiceResponse

DDataTransferObject

Attempts:

3 left

💡 Hint

Common Mistakes

Using internal models as input instead of external models.

The Anti-corruption Layer translates from the external model, so the input should be the external model.

2fill in blank

medium

Complete the code to implement the Anti-corruption Layer adapter method.

Microservices

public InternalModel adapt([1] external) {
    // mapping logic
    return new InternalModel();
}

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

AServiceRequest

BInternalModel

CExternalModel

DDataEntity

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing input and output types in the adapter method.

The adapter method takes an external model as input to convert it into an internal model.

3fill in blank

hard

Fix the error in the Anti-corruption Layer pattern where the internal system is directly coupled to the external system.

Microservices

public class InternalService {
    private ExternalService externalService;

    public void process() {
        var data = externalService.getData();
        var internalData = [1](data);
        // process internalData
    }
}

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

AexternalService.getData

BinternalService.transform

CexternalService.processData

Dnew Adapter().adapt

Attempts:

3 left

💡 Hint

Common Mistakes

Calling external service methods directly without translation.

The internal service should use an adapter to translate external data, avoiding direct coupling.

4fill in blank

hard

Fill both blanks to complete the request flow through the Anti-corruption Layer.

Microservices

ExternalSystem -> [1] -> [2] -> InternalSystem

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

AAntiCorruptionLayer

BExternalAPI

CInternalAPI

DAdapter

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing the order of components in the flow.

The request first hits the External API, then passes through the Anti-corruption Layer before reaching the internal system.

5fill in blank

hard

Fill both blanks to complete the dictionary comprehension for filtering and transforming data in the Anti-corruption Layer.

Microservices

filtered_data = {k:v for k, v in data.items() if v [1] 10 and 'valid' [2] k}

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

A:

B>

Cin

D<

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong operators or missing colon in comprehension.

The dictionary comprehension uses ':' to map keys to values, filters values greater than 10, and keys containing 'valid'.

Practice

1. What is the main purpose of an Anti-corruption layer in microservices architecture?

easy

A. To translate and isolate differences between two systems to prevent corruption

B. To speed up database queries between microservices

C. To store user session data securely

D. To monitor network traffic between services

Solution

1. Step 1: Understand the role of the anti-corruption layer

   The anti-corruption layer acts as a translator between two systems with different models or rules.

2. Step 2: Identify its main goal

   Its goal is to prevent the internal system from being affected or corrupted by external system differences.

3. Final Answer:

   To translate and isolate differences between two systems to prevent corruption -> Option A

4. Quick Check:

   Anti-corruption layer = Translation and isolation [OK]

Hint: Think: 'translator' between systems to avoid confusion [OK]

Common Mistakes:

• Confusing it with caching or monitoring layers
• Thinking it speeds up queries directly
• Assuming it stores user data

2. Which of the following is the correct way to implement an anti-corruption layer between two microservices?

easy

A. Directly expose the legacy system's database schema to the new service

B. Allow the new system to write directly to the legacy system's tables

C. Use the same data model in both systems without changes

D. Create a translation interface that maps legacy data to the new system's model

Solution

1. Step 1: Review implementation best practices

   An anti-corruption layer should translate and map data between systems, not share schemas directly.

2. Step 2: Identify the correct approach

   Creating a translation interface that maps legacy data to the new system's model isolates differences and protects both systems.

3. Final Answer:

   Create a translation interface that maps legacy data to the new system's model -> Option D

4. Quick Check:

   Translation interface = Correct implementation [OK]

Hint: Map legacy data to new model, never share schemas directly [OK]

Common Mistakes:

• Exposing legacy database schema directly
• Using identical data models without translation
• Allowing direct writes to legacy tables

3. Given the following pseudo-code for an anti-corruption layer translating legacy user data, what will be the output?

legacyUser = {"fullName": "Jane Doe", "age": 30}

function translateUser(legacy) {
  return {
    name: legacy.fullName,
    isAdult: legacy.age >= 18
  }
}

newUser = translateUser(legacyUser)
console.log(newUser)

medium

A. {"name": "Jane Doe", "isAdult": false}

B. {"fullName": "Jane Doe", "isAdult": true}

C. {"name": "Jane Doe", "isAdult": true}

D. {"name": "Jane Doe"}

Solution

1. Step 1: Analyze the translation function

   The function creates a new object with 'name' from 'fullName' and 'isAdult' as true if age >= 18.

2. Step 2: Apply the function to the legacy user

   legacyUser has fullName 'Jane Doe' and age 30, so isAdult is true.

3. Final Answer:

   {"name": "Jane Doe", "isAdult": true} -> Option C

4. Quick Check:

   Translate fullName and check age >= 18 = true [OK]

Hint: Check property mapping and age condition carefully [OK]

Common Mistakes:

• Using legacy property names in output
• Incorrectly evaluating age condition
• Missing one of the output properties

4. A developer wrote this anti-corruption layer code snippet but it causes errors when legacy data is missing some fields:

function translateOrder(legacyOrder) {
  return {
    id: legacyOrder.orderId,
    total: legacyOrder.amount.value,
    status: legacyOrder.status.toUpperCase()
  }
}

What is the main issue and how to fix it?

medium

A. The function should return legacyOrder directly without changes

B. The code assumes nested fields exist; add checks to handle missing or undefined fields

C. Use lowercase for status instead of toUpperCase()

D. Remove the id field to avoid errors

Solution

1. Step 1: Identify the error cause

   The code accesses nested fields like legacyOrder.amount.value without checking if amount exists, causing errors if missing.

2. Step 2: Fix by adding safety checks

   Use conditional checks or optional chaining to safely access nested fields and avoid runtime errors.

3. Final Answer:

   The code assumes nested fields exist; add checks to handle missing or undefined fields -> Option B

4. Quick Check:

   Missing field checks cause errors = add safety checks [OK]

Hint: Always check nested fields exist before accessing [OK]

Common Mistakes:

• Ignoring null or undefined nested objects
• Returning legacy data without translation
• Changing case without reason
• Removing necessary fields

5. You need to integrate a legacy billing system with your new microservice. The legacy system uses different currency codes and date formats. How should you design the anti-corruption layer to handle this integration effectively?

hard

A. Build a translation layer that converts legacy currency codes to standard ISO codes and normalizes date formats before passing data to the new service

B. Modify the legacy system to use the new system's currency codes and date formats directly

C. Ignore currency and date differences and pass data as-is to the new service

D. Store all legacy data in the new system without any translation

Solution

1. Step 1: Identify integration challenges

   Legacy system uses different currency codes and date formats, which can cause data misinterpretation.

2. Step 2: Design translation in anti-corruption layer

   Create a layer that converts legacy currency codes to standard ISO codes and normalizes date formats to the new system's expected format.

3. Final Answer:

   Build a translation layer that converts legacy currency codes to standard ISO codes and normalizes date formats before passing data to the new service -> Option A

4. Quick Check:

   Translate legacy formats to standard before integration [OK]

Hint: Translate legacy formats to standard before integration [OK]

Common Mistakes:

• Trying to change legacy system directly
• Passing data without translation
• Storing legacy data without normalization