Cloud computing capstones are judged on the architecture diagram as much as the code — panels want to see you understand why each service was chosen. These ideas each map to a clear, explainable architecture.
A full CRUD app built entirely on managed services — a strong choice for explaining cost/scaling trade-offs.
Load-balanced, auto-scaling deployment demonstrated under simulated traffic load.
A unified interface backing up data across two providers — good for a redundancy/disaster-recovery narrative.
GitHub Actions/Jenkins pipeline auto-deploying a containerized app to the cloud on every push.
A small multi-service app orchestrated with Kubernetes — ambitious, but a strong DevOps/cloud talking point.
Upload-triggered serverless transcoding pipeline (e.g. Lambda + S3 + MediaConvert-style flow).
Sensor data ingested via a cloud message queue, processed, and visualized on a live dashboard — bridges IoT and cloud in one build.
A multi-region deployment demonstrating failover — mostly an architecture/documentation exercise, lighter on code.