Tapau (Friend on Campus)
Peer-to-peer campus errand app, running on a closed credit economy
Live demo ↗ (until ~10 Dec 2026)Repository ↗
Problem
Students need things picked up on campus while they're stuck elsewhere. Tapau lets peers fulfil errands for non-cashable credits.
My role
Team of 4 (CS3219, NUS). Owned cloud architecture, infrastructure as code (Terraform), deployment and CI/CD, authentication, and the User Service.
What I built
- System: Event-driven microservices (User, Order, Credit, Supplier) behind an nginx API gateway, database-per-service. Async messaging over RabbitMQ with retry and dead-letter queues, and correlation IDs for distributed tracing.
- Infra as code: Terraform: CloudFront → ALB → ECS Fargate in private subnets, RDS Postgres, secrets in SSM, CloudWatch dashboards. Remote state, zero click-ops.
- CI/CD: Path-filtered CI (typecheck, tests, Docker build, Trivy CVE scan, terraform validate) behind one required check, so only changed services ship on every merge. CD builds immutable SHA-tagged images and does zero-downtime rolling deploys to ECS by digest, with circuit-breaker auto-rollback, smoke tests and SNS alerting. Keyless AWS auth via OIDC.
- Auth & User Service: Keycloak OIDC/JWT with RBAC, server-enforced sign-up rules, session-revocation checks on every service, compensating rollback on failed provisioning, and two-admin approval for role escalation.
Also supported
- Choreography-based saga (order ↔ credit reservation)
- Transactional outbox pattern
- Idempotent event consumers
Stack
- TypeScript
- Node.js / Express 5
- React
- PostgreSQL
- Keycloak (OAuth 2.0 / OIDC)
- RabbitMQ
- nginx
- Docker
- AWS ECS Fargate
- RDS
- ALB
- CloudFront
- ECR
- EFS
- SSM
- CloudWatch
- Terraform
- GitHub Actions
- Trivy
Screenshots

