How should you design the anti-corruption layer to handle this integration effectively?
hard📝 Trade-off Q15 of 15
Microservices - Migration from Monolith
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?
ABuild a translation layer that converts legacy currency codes to standard ISO codes and normalizes date formats before passing data to the new service
BModify the legacy system to use the new system's currency codes and date formats directly
CIgnore currency and date differences and pass data as-is to the new service
DStore all legacy data in the new system without any translation
Step-by-Step Solution
Solution:
Step 1: Identify integration challenges
Legacy system uses different currency codes and date formats, which can cause data misinterpretation.
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.
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
Quick Check:
Translate legacy formats to standard before integration [OK]
Quick Trick: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
Master "Migration from Monolith" in Microservices
9 interactive learning modes - each teaches the same concept differently
