Pick a problem and start prompting.
Multiple Data sources: s3, pgdb Aggregation on long timeframes (30d, 60d, 90d, etc) calculated on the fly per frontend requests gives bad UX. Load time for web page is usually >10s
Track how many times each piece of content has been viewed. The counter must be fast to increment and accurate enough for analytics.
Engineers need to toggle features on or off for specific users or percentages of traffic without redeploying code.
Monitor whether each service in a fleet is up and responding correctly. Alert on-call engineers when a service goes down.
Build a simple distributed key-value store that supports get, put, and delete operations with low latency.
A mobile game needs a real-time leaderboard showing the top players by score. Rankings must update within seconds.
Users want to share snippets of text or code via a short link. The paste should expire after a configurable time.
Users can create polls, cast votes, and see live results. Design for correctness under concurrent votes and real-time result updates.
Users submit a URL or text and receive a scannable QR code image. The service must handle high request volume with low latency.
An API needs to limit how many requests a client can make in a given time window to prevent abuse.
A web application needs to store and retrieve user session data with millisecond latency and automatic expiry.
Applications emit log lines at high throughput. Design a system to ingest, store, and query logs by service name and time range.
Make long links shorter and trackable. Users paste a URL and get a short alias that redirects to the original.
A product launch needs a waitlist where users sign up, receive a unique referral link, and move up the queue by referring others.
A game needs rankings that refresh quickly as scores change, and users expect the ordering to feel current and fair.
Users want to publish short snippets of text or code and retrieve them later through a compact URL, sometimes with expiration.
Users create polls, cast votes concurrently, and expect the displayed totals to stay responsive and trustworthy.
Operators need a reliable way to detect failing services across a fleet and alert the right people quickly.
Users provide text or links and expect a generated QR image quickly, even during bursts of traffic.
Services need to read and update small pieces of shared state quickly, with low latency and predictable behaviour under load.
