Case study · Dec 2025 – Present
ZenDSA
A live DSA learning platform with spaced repetition and LLM-powered hints.
- RoleSolo: designed, built, deployed, and operate it
- Result37 registered users
- Result120+ problems across 15 topics
The problem
Solving a data structures problem once does not mean you can solve it again in an interview weeks later. ZenDSA schedules reviews with spaced repetition and gives an LLM-powered hint when you are stuck.
What it looks like

How a request flows
A Spring Boot REST API on PostgreSQL, containerized with Docker and deployed on Render. The Next.js frontend runs on Vercel. GitHub Actions runs CI.
- Actuator health checks
- Trace ID on every log line
- Structured JSON errors
- Tuned HikariCP pool
Decisions that shaped it
A fallback chain for LLM hints
Hints come from OpenRouter and Groq. Providers fail and rate-limit, and a missing hint breaks the learning flow. So hint requests go through a fallback chain: if one provider fails, the request moves to the next one and the learner still gets a hint.
Observability before features
I run production alone, so problems have to be easy to see. The API has Actuator health checks, structured JSON errors, and a trace ID on every log line, so I can follow any request end to end. The HikariCP connection pool is tuned for the database it talks to.
Keep the source private
ZenDSA is a live product with real users, so the code is private. This page shows how it works instead, and I am happy to walk through the code in an interview.
What broke, and the fix
BrokeLLM providers failed and rate-limited
FixHint requests now fall back to the next provider instead of failing.
BrokeThe LLM proxy could be pointed at hosts it should never reach (SSRF)
FixI found this in my own security audit and fixed it with allowlist validation before any user was exposed.
Proposed design · not deployed
How I would run ZenDSA on AWS
ZenDSA runs on Render and Vercel today, and at its current size that is the right call. This is the AWS design I would move it to if it outgrew them, built on what I learned for the AWS Certified Cloud Practitioner exam. It is a design, not something I have deployed.
CloudFront, S3 and WAF
Serve the frontend from the edge and put rate limits in front of the hint endpoint, because every hint costs an LLM call.
ECS Fargate, not Lambda, for the API
The Spring Boot API keeps a warm JVM and a HikariCP pool to PostgreSQL. A long-running container fits that, the Docker image moves over as it is, and there are no cold starts on user requests.
RDS PostgreSQL in private subnets
The data already lives in PostgreSQL, so the schema stays. Automated backups come built in, and Multi-AZ can be switched on when uptime matters more than cost.
DynamoDB where key-value fits
A hint cache with a time-to-live, so a repeated hint does not cost a second LLM call, and the lock table for Terraform state. Not as a replacement for PostgreSQL.
NAT gateway for outbound calls
The API has no public IP but can still reach the LLM providers. The URL allowlist from the SSRF fix still decides where it may call.
Secrets Manager and IAM task roles
Database credentials and LLM API keys stay out of images and environment files. Only the API task role can read them.
CloudWatch
Logs, metrics and alarms in one place. The trace IDs the API already logs become searchable across requests.
Lambda with EventBridge
Scheduled jobs run on their own, so the API container only serves requests.
Client VPN
Admin access to the private database without a public endpoint. For one person, SSM Session Manager would be the cheaper option.
Terraform
Separate network, data, compute and edge modules. State in S3 with a DynamoDB lock. GitHub Actions runs plan on every pull request and apply on merge, using an OIDC role instead of long-lived keys.
| Trade-off | Render today | AWS design |
|---|---|---|
| Cost | Low, and close to zero when idle | A fixed monthly floor for NAT, the load balancer and RDS, even with no traffic |
| Operations | The platform handles networking and patching | I own the network, upgrades and alarms |
| Isolation | Shared platform networking | API and database in private subnets, no public IPs |
| Scaling | Pick a bigger plan | ECS autoscaling on CPU or request count |
| Rebuilding | Settings live in a dashboard | Everything is in Terraform and can be rebuilt from Git |
My call: stay on Render until traffic or uptime needs justify AWS's fixed monthly cost. With the whole design in Terraform, the move would be a planned change, not a rebuild by hand.
Results
- 37 registered users
- 120+ problems across 15 topics
- Live at zendsa.vercel.app
- Java
- Spring Boot
- PostgreSQL
- Docker
- Next.js
- TypeScript
- OpenRouter
- Groq
- GitHub Actions
- Render
- Vercel
Source code is private.