Hey everyone
I’ve been working on a full-stack digital banking platform called Alvor Bank, built with:
- .NET 10 (microservices + Clean Architecture)
- Angular 21 (monorepo-style frontend)
- PostgreSQL, RabbitMQ, YARP API Gateway
- Docker & GitHub Actions CI/CD
To move beyond “hello world” tutorials, I put together a small architecture & quality roadmap for the system, and I’m sharing the slides here.
In the slides you can see:
-The high-level architecture diagram
-VS solution structure and how the projects are organized
-How I enforce test coverage as a quality gate
-A glimpse of the CI/CD pipeline (build, test, lint, Docker)
-The security/IAM setup (centralized auth, roles, tenants)
-The final project scope for the platform
I’m also documenting everything step-by-step in an early-access book where I build this system from scratch, chapter by chapter:
Modern Full-Stack Banking Microservices (in progress on Leanpub)
https://leanpub.com/fullstack-banking-microservices
I’d really like to hear from other engineers here:
How do you enforce quality gates (tests, coverage, linting, security) in your own projects?
Happy to discuss architecture choices, trade-offs, or anything in the slides.
I’m not building another TODO app. I’m building a production-grade digital bank. Here's what that actually looks like in code
System overview: Microservices, event-driven notifications, and full IAM
Real project structure: Clean Architecture layers, separate service projects, shared building blocks.
We treat tests as a priority, not an afterthought. Coverage gates in CI ensure quality
Everything ships through CI/CD from day one. Green builds and enforced quality thresholds
Coverage report test on CI/CD from Gih=thub Actions
This is from my book Modern Banking Microservices with Clean Architecture, DDD, TDD, .NET 10, and Angular 21 (nx Monorepo). Go beyond tutorials. Build systems that matter. Link: 1: https://leanpub.com/fullstack-banking-microservices.
