Response body — /projects
Four systems.
Each one taught me something painful.
Real-world backend systems and the trade-offs that
didn't show up in the requirements doc.
Response metadata
Multi-Tenant Distributed ERP Platform
One database for every store meant one bad query could tank everyone's performance — and every store needed to keep working when the network didn't.
A distributed ERP system designed for multi-store environments with per-tenant databases and centralized synchronization.
The hard part
Building a sync protocol that handles offline stores rejoining without data collisions — solved via event-sourced reconciliation with deterministic conflict resolution and per-tenant boundaries.
Peer-to-Peer Payment Workflow System
Payment state machines that look simple in diagrams break the moment a webhook is late or a gateway returns ambiguously.
A backend system designed to facilitate secure peer-to-peer payments using a third-party payment gateway.
The hard part
The gateway confirmed but our webhook timed out — built a reconciliation job that closes the gap without double-charging, using idempotency keys keyed to user-intent rather than request-id.
Private Secure Data Transfer Platform
Sharing files between machines on different networks usually means trusting a third party with your data or exposing a service to the open internet.
A personal project exploring secure, private data transfers using encrypted tunnels and controlled access.
The hard part
Designing a transfer flow that never opens an inbound port — Cloudflare Tunnel + SSH key gating + per-session ephemeral credentials, so the attack surface is a moving target instead of a public address.
Secure Healthcare Metrics Tracking System
Healthcare-adjacent data needs the same access discipline as clinical data, but the team didn't have the compliance overhead to staff it.
A backend platform designed to securely collect and manage healthcare-related operational metrics with strict access control and compliance awareness.
The hard part
Designing an RBAC layer that maps cleanly to audit requirements without turning every feature into a policy negotiation — pre-baked role bundles, JWT claims that mirror table-level grants, and a deny-by-default posture at the API edge.
End of response · 4 items