feat: complete Yape code challenge - Anibal Vergaray #524
Conversation
This file contains hidden or 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
anivermo99
changed the title
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.
Hey Yape Team!
This PR wraps up the Yape Code Challenge with the full implementation plus a detailed README. Inside you’ll find:
The problem overview and a neat flowchart.
The tech stack I used (NestJS, Prisma, Kafka, Redis, and more).
Examples of the API requests and responses.
How I tackled high volume scenarios with caching, idempotency, OCC, and event-driven design.
Clear instructions on how to run everything with Docker Compose or locally using scripts and env vars.
Feel free to take a look and let me know if you have any questions or suggestions!
Thanks!