I build backend systems that are secure, scalable, and ready for production — not just for demos. Full-stack, from architecture to deployment.
They're architecture decisions made too fast, too early. I've spent the last three years building systems where getting it wrong has real consequences — payment flows where a race condition means lost money, auth systems where a misconfigured token means a data breach.
That experience changed how I approach every project. I don't start with the framework. I start with the question: what breaks first, and why?
I design the architecture, write the backend, wire the frontend, and ship to production. One person, the full picture — which means no gaps in understanding between layers.
End-to-end escrow payment platform covering all markets supported by PawaPay — 30+ African countries, one integration. Built on PawaPay's unified mobile money API, containerized the full stack, hardened Nginx behind Cloudflare, and tuned Redis for payment safety. The kind of system where data integrity isn't optional.
Built a production-grade authorization server from scratch — not a Keycloak wrapper. Custom JPA persistence, PKCE, MFA/TOTP, Device Code flow (RFC 8628), and multi-tenant JWT customization using Java 21 sealed interfaces. Integrated Angular frontend via BFF pattern with Spring Cloud Gateway and Consul.
Architected around one constraint: zero data corruption under concurrent load. Hexagonal architecture to isolate domain logic, pessimistic locking at the PostgreSQL level, HikariCP tuning, and Java 21 virtual threads. Held integrity under stress-tested concurrent scenarios where optimistic locking would have failed.
12-month intensive program built on Holberton School's curriculum. Covered systems programming in C, algorithms, data structures, web development, and full-stack engineering. One of the most rigorous software programs on the continent — known for its high dropout rate.
Foundational and advanced studies in computer science — covering software engineering principles, databases, networking, and systems design.
Tell me about your project. I'll tell you honestly whether I can help, how long it takes, and what it costs. No pitch, no pressure.
Come with a problem, not a job description. The more concrete your situation, the better the conversation.
If your startup needs a backend that won't wake you up at 3am — or if you need someone who thinks about what happens six months later — reach out.
hello@saintbassanaga.com