Backend Challenge: Clean Architecture + Kafka + Prisma #551
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
…/transactions/:id
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Implementé la funcionalidad completa de creación y consulta de transacciones siguiendo Clean Architecture.
Cada transacción se valida con reglas básicas de anti-fraude:
Transacciones mayores a 1000 se marcan como rejected.
El resto se marcan como approved.
Integré Kafka para publicar eventos de creación de transacciones y para consumir la respuesta del microservicio de validación.
Uso de Prisma como ORM para persistencia en PostgreSQL.
Estructura modular: domain (entities, use-cases, repositories), infra (DB, Kafka), api (controllers, routes).