Feat/sprint 03 payment domain - #1
Merged
Merged
Conversation
…Sprint 3; update related documentation
…s; add unit tests
…nt PaymentRepositoryInterface
…neratorInterface; update Payment validation
…d implementation of the CreatePayment use case
…d package to generate uuid
…ment Model, add http route for saving payments, add Dependency Inversion for PaymentRepository and UuidIdGenerator and update sprint 003 status
…through http endpoint with validation
…ment at PaymentRepository
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
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.
Sprint 3 — Payment Domain
Objetivo
Concluir a Sprint 3 — Payment Domain, implementando o primeiro fluxo funcional de criação de pagamentos e estabelecendo a base do domínio financeiro do microsserviço.
A implementação segue a arquitetura definida nas sprints anteriores, mantendo as responsabilidades separadas entre HTTP, Application, Domain, Repository Interface e Infrastructure.
Principais alterações
Domain
Payment.PaymentStatus.Application
CreatePayment.CreatePaymentInputeCreatePaymentOutput.IdGeneratorInterface.Infrastructure
PaymentRepositoryInterface.PaymentRepository.Payment.payments.HTTP
POST /payments.PaymentController.Testes
Foram adicionados testes para as principais camadas do fluxo:
Payment.CreatePayment.PaymentRepository.POST /payments.Fluxo arquitetural
O fluxo implementado segue:
A implementação mantém o domínio desacoplado de frameworks, banco de dados e detalhes de infraestrutura.
Documentação
Também foram atualizados:
readme.mdchangelog.mddocs/planning/sprint-003.mddocs/planning/roadmap.mddocs/adr/ADR-003-payment-domain-first.mdCritérios de aceite
Paymentimplementada com invariantes.CreatePaymentimplementado.POST /paymentsimplementado.Resultado
Com esta Sprint, o projeto passa a possuir seu primeiro fluxo de negócio completo, desde a entrada HTTP até a persistência do pagamento, mantendo as responsabilidades separadas conforme Clean Architecture e DDD.
As próximas etapas poderão evoluir a partir dessa base para mensageria, processamento assíncrono, auditoria, observabilidade e infraestrutura AWS.
Branch:
feat/sprint-03-payment-domainTarget:
mainSprint:
Sprint 3 — Payment Domain