Skip to contentSkip to content
Verified credentials. On-chain. Forever.Learn more
Ewance
Sign in
Cover image for Choose a Sidecar Cache Store for a Hotel-Search API
Design

Choose a Sidecar Cache Store for a Hotel-Search API

FreeVerified credential2 weeksIntermediate

Overview

What this challenge is about.

Choose a Sidecar Cache Store for a Hotel-Search API. Intermediate challenge in design. Designing real products under real constraints, earn a blockchain-veri...

CredentialBlockchain-anchored
ShareableLinkedIn-ready
LanguageEnglish
PaceSelf-paced

The Brief

What you'll do, and what you'll demonstrate.

Decide which of Redis, KeyDB, or DragonflyDB should serve as Voa's in-memory sidecar cache, and prove the choice against the team's real traffic.

This is not a design exercise. It is the work a product designer does between a brief and a shipped interface. That distinction matters to every hiring manager who has seen candidates redesign Spotify's homepage and none who have worked under real product constraints.

When you finish, you will have something most graduates do not: a real-world deliverable, verified by Ewance, that you can show to a hiring manager and say "I did this. Here is the proof."

Earning criteria — what you'll demonstrate

  • Translate a captured production workload into a faithful, repeatable benchmark setup.
  • Measure and interpret median versus tail latency, throughput, and memory efficiency under sustained load.
  • Compare in-memory stores on operational properties — replication, failover, and snapshotting — that affect a small team.
  • Write a decision memo that ties a recommendation to evidence and states revisit triggers.
  • Sequence a low-risk production rollout with a feature flag and a rollback path.

Program Fit

Where this fits in your program.

Sharpens the same skills your degree expects you to demonstrate.

Aligned coursework coming soon.

Careers

Career paths this challenge builds toward

Completing this challenge demonstrates skills that transfer directly to these roles:

Backend Engineer

Selecting and proving an in-memory cache against real traffic is core backend work; this challenge builds the habit of grounding infrastructure choices in measured evidence and shipping them safely behind a flag.

This challenge sharpens

  • nosql
  • cache-design
  • benchmarking

Platform Engineer

Platform teams own the data stores other services depend on. Comparing replication, failover, and snapshotting across engines and writing a defensible recommendation mirrors the day-to-day judgment a platform role demands.

This challenge sharpens

  • operational-properties
  • redis
  • decision-memos

Site Reliability Engineer

Reliability hinges on knowing how a system behaves under sustained load and how it recovers from failure. Benchmarking tail latency and planning a low-risk rollout with rollback are direct SRE competencies.

This challenge sharpens

  • benchmarking
  • operational-properties
  • cache-design

One more thing

You can put a credential on your CV by Friday.