Techcookies — System Design & Interview Prep for Engineers

🍪 TechCookies

Concepts Practice SD challenges Pricing NextJS Q&A

Log in Start free

🍪 TechCookies

Concepts Practice SD challenges Pricing Privacy Terms

© 2026 TechCookies

Concepts

◈A/B Testing SystemsPro

◈Adaptive Bitrate Streaming (HLS/DASH)Pro

◈Analytics PipelinesPro

◉Append-Only Audit Tables

◈Async Job Processing FundamentalsPro

◈Async Processing PipelinesPro

◈Audio Streaming ArchitecturePro

◈Authentication FundamentalsPro

◈Authorisation and RBACPro

◈Canvas and WebGL RenderingPro

◉Back-of-Envelope Estimation

◉Circuit Breakers

◉Client-Side Caching

◈Consistent hashingPro

◈Conflict-Free Replicated Data Types (CRDTs)Pro

◈Cross-Tab SynchronisationPro

◉Database Constraints as Data Guards

◉Database Indexes: Making Queries Fast

◉Relationships and Foreign Keys

◈Databases & storagePro

◈Dead-Letter QueuesPro

◈At-Least-Once vs Exactly-Once DeliveryPro

◈Delta SyncPro

◈Distributed Payment ArchitecturePro

◈Drag-and-Drop ArchitecturePro

◈End-to-End Encryption in the BrowserPro

◈Edge Computing and CDN ArchitecturePro

◈Microcontroller and Embedded ConstraintsPro

◉Event-Driven Architecture

◉Exponential Backoff and Retry

◉Failure Modes in Distributed Systems

◈File API and File System Access APIPro

◈File Security and DeduplicationPro

◉Frontend Architecture Patterns

◈Geolocation and Permissions APIPro

◈Geospatial QueriesPro

◉Graceful Degradation and Fallbacks

◈Grid Layout and Widget SystemsPro

◈IndexedDB for Browser-Side StoragePro

◉Infinite Scroll and Pagination

◈Intersection Observer APIPro

◈IP-Based LocalisationPro

◈Kafka Deep DivePro

◈Last-Write-Wins Conflict ResolutionPro

◉Lazy Loading Images and Media

◉Virtualisation and Large Lists

◉Load balancing

◈Message Queue FundamentalsPro

◈Message queuesPro

◈Object Storage (S3-Compatible)Pro

◈Logging and ObservabilityPro

◈Offline-First ArchitecturePro

◈Offline-Capable Hardware SystemsPro

◈Operational Transform (OT)Pro

◈Password SecurityPro

◈Payment Integration FundamentalsPro

◈Presence and AwarenessPro

◈Provider Adapter PatternPro

◈Queue-per-Channel PatternPro

◈Rate Limiting AlgorithmsPro

◈Rate Limiting in PracticePro

◉Server State with React Query

◉Read Replicas and Write Scaling

◈Real-Time Location TrackingPro

◈Real-Time State ManagementPro

◉Redis Deep Dive

◉REST API Design Principles

◈Scheduled Jobs and CronPro

◉Schema Design Fundamentals

◈Server-Sent Events (SSE)Pro

◈Service WorkersPro

◈SQS and Managed QueuesPro

◈State Machines on the FrontendPro

◉Stateless Service Design

◉Synchronous vs Asynchronous Communication

◈Third-Party API ResiliencePro

◈Three-Way MergePro

◈Time-Series and Columnar DatabasesPro

◉Vertical vs Horizontal Scaling

◈Video Processing PipelinesPro

◈Web Audio APIPro

◈Web Crypto APIPro

◈Web Workers for Heavy ComputationPro

◈Webhooks: Receiving External EventsPro

◈WebSocket ArchitecturePro

◉WebSockets vs SSE vs Polling

◈When to Use NoSQLPro

◈Worker Pool PatternPro

◈Yjs in PracticePro

◉State Management with Zustand

SD challenges

↗arcade game card payment system at scalePro ↗mall and amusement park kiosk payment systemPro View all →

System design › Concepts › At-Least-Once vs Exactly-Once Delivery

◈At-Least-Once vs Exactly-Once DeliveryPro~30 min · avg 65%

🔒

Pro content

At-Least-Once vs Exactly-Once Delivery is a Pro concept. Upgrade to access full content, practice questions, and design challenges.

Upgrade to Pro →

📝 NotesAt-Least-Once vs Exactly-Once Delivery

Sign in to save notes across sessions.