All outcomes
Skills

Implement Cloud-Native Design Patterns on a Real Deployment

10 weeks · 0 milestones

Implement 3–5 cloud-native design patterns — circuit breaker, bulkhead, retry with exponential backoff, saga, or event sourcing — on a real deployment on AWS, GCP, or Azure, producing a working system with a deployment URL the reviewer can access. For each pattern implemented, write a trade-off analysis explaining: why this pattern was chosen over alternatives, what failure scenario it addresses, and what complexity cost it introduces. The running deployment is the proof that the patterns actually exist in the system, not just in a diagram. Proof: a cloud architect or senior SRE inspects the running deployment during the review and asks 'what happens if I call this endpoint while the circuit is open?' — you must demonstrate the live behaviour, not describe it from the documentation.

Milestone map

Milestone map

3 milestones

Implement an application consisting of at least three communicating services, each containerised with Docker, and orchestrated with Docker Compose or Kubernetes. The application must implement at least two of the following patterns: API gateway, circuit breaker, service discovery, event-driven communication, or sidecar. Deploy to a cloud platform (any major provider has a free tier).

Proof required

Submit: a public GitHub repository containing the application code, Dockerfiles for each service, and an orchestration configuration file (docker-compose.yml or Kubernetes manifests); a README documenting the architecture and the two patterns implemented; and a live URL or screenshot proving the application is deployed and reachable. A senior cloud engineer or architect must review the repository and confirm in writing that the patterns are correctly implemented.

What gets checked

  • Three or more communicating services, each containerised, with orchestration configuration committed to the repository
  • Two cloud-native patterns are demonstrably implemented — not described in a README without code evidence
  • A senior cloud engineer or architect has confirmed in writing that the patterns are correctly implemented

We use analytics to improve Powstik. No ads, ever.