Forex MTL Assignment #61
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a submission for Forex MTL Interview Assignment.
The main idea is we implement a caching mechanism using Redis and store all possible PAIRs every 5 minutes.
Considering a scenario with three currencies—USD, SGD, and JPY—we store all possible exchange rate pairs in Redis, resulting in six keys: USDSGD, USDJPY, JPYUSD, SGDUSD, JPYSGD, and SGDJPY. When a user requests exchange rates, the system first checks the Redis cache. If the requested pair is found, the corresponding rate is returned immediately. Otherwise, the system proceeds with the caching process, storing the PAIRs in Redis and setting an expire time to 5 minute.
This approach minimizes response time, requiring a maximum of 288 requests under worst-case conditions.
You can read more about how I design the documentation on README.md.