A realistic reference architecture for an event-driven banking platform on AWS, combining domain events, service selection, FinOps, security and observability.
- Production: AWS Event-Driven FinOps Platform
- Documentation: Project docs
- GitHub: fernandofatech/aws-event-driven-finops-platform
- Author: Fernando Francisco Azevedo · LinkedIn · GitHub
This public repository is part of a bilingual portfolio focused on solution architecture, AWS, AI, MCP/tooling, DevSecOps, and production-ready engineering practices.
Este repositório público faz parte de um portfólio bilíngue focado em arquitetura de soluções, AWS, IA, MCP/tools, DevSecOps e boas práticas de engenharia para produção.
The fictional platform models a banking event mesh with events such as:
AccountOpenedPixPaymentRequestedTransactionAuthorizedFraudRiskScoredStatementGenerated
- Amazon EventBridge for domain event routing.
- Amazon SQS for buffering and decoupling.
- Amazon Kinesis Data Streams for ordered streaming.
- Amazon MSK for Kafka-compatible high-volume workloads.
- AWS Lambda and Step Functions for serverless processing.
- DynamoDB for idempotency and event state.
- CloudWatch and X-Ray for observability.
- Shows real trade-offs between AWS event services.
- Treats cost as an architectural requirement.
- Documents event contracts and ADRs.
- Includes tests for decision logic.
- Uses CI and GitFlow-compatible contribution guidance.
- Includes a static frontend in
frontend/ready for Vercel deployment. - Automates CodeQL, Trivy, Gitleaks, dependency review and package audits.
python -m pip install -e . pytest
pytest -qcd frontend
npm ci
npm run lint
npm run buildThe frontend is intentionally static and dependency-light to keep the portfolio demo fast, secure and easy to deploy.
See OPERATIONS.md for GitFlow, Vercel secrets and security pipeline details.