Latest AI Performance Verification List in System Design | Orivel

Benchmark Genres

View all 333 Discussions 70 Creative Writing 18 Coding 17 System Design 17 Education Q&A 16 Explanation 15 Summarization 17 Idea Generation 16 Roleplay 15 Business Writing 16 Planning 16 Analysis 17 Brainstorming 15 Persuasion 16 Humor 16 Empathy 18 Counseling 18

Model Directory

View all GPT-5.4 (OpenAI) GPT-5.2 (OpenAI) GPT-5 mini (OpenAI) Claude Opus 4.6 (Anthropic) Claude Sonnet 4.6 (Anthropic) Claude Haiku 4.5 (Anthropic) Gemini 2.5 Pro (Google) Gemini 2.5 Flash (Google) Gemini 2.5 Flash-Lite (Google)

System Design

Google Gemini 2.5 Pro VS OpenAI GPT-5 mini

Design a URL Shortening Service at Scale

You are tasked with designing a URL shortening service (similar to bit.ly or tinyurl.com) that must handle the following constraints: 1. The service must support 100 million new URL shortenings per month. 2. The read-to-write ratio is 100:1 (i.e., 10 billion redirects per month). 3. Shortened URLs must be at most 7 characters long (alphanumeric). 4. The system must guarantee that a shortened URL, once created, never expires unless explicitly deleted by the user. 5. Redirect latency (from receiving the request to issuing the HTTP 301/302) must be under 10 milliseconds at the 99th percentile. 6. The system must remain available even if an entire data center goes offline. 7. The service must support an optional analytics dashboard showing click counts, geographic distribution, and referrer data per shortened URL, but analytics must not degrade redirect performance. Provide a comprehensive system design that addresses: A. High-level architecture: Describe the major components and how they interact. B. URL generation strategy: How you generate unique short codes, why you chose that approach, and how you handle collisions. C. Data model and storage: What databases or storage systems you use and why. Include schema considerations. D. Read path optimization: How you achieve the latency requirement for redirects at the given scale. E. Write path: How new URLs are created and persisted reliably. F. Scaling strategy: How the system scales horizontally to handle growth. G. Reliability and fault tolerance: How you handle data center failures, replication, and failover. H. Analytics pipeline: How you collect, process, and serve analytics data without impacting redirect performance. I. Key trade-offs: Identify at least three significant trade-offs you made in your design and justify each one. Be specific about technologies, protocols, and numerical estimates where relevant (e.g., storage calculations, QPS estimates, cache sizes).

51

Mar 18, 2026 22:59

System Design

Anthropic Claude Sonnet 4.6 VS OpenAI GPT-5 mini

Design a Scalable Real-Time Notification System

You are a senior software engineer tasked with designing a real-time notification system for a rapidly growing social media platform. The system must be able to deliver notifications (e.g., 'new like', 'new comment', 'friend request') to users who are currently online. **System Requirements:** * **Functional:** 1. Users can subscribe to different notification topics (e.g., updates on their own posts, updates from specific friends). 2. An event publishing service can send messages to specific topics or users. 3. Subscribed, online users receive relevant notifications in real-time. * **Non-Functional (Constraints):** 1. **Scalability:** The system must support 1 million concurrent online users and a peak load of 10,000 notifications per second. 2. **Latency:** 99% of notifications should be delivered to the user's device within 200 milliseconds from the time the event is published. 3. **Reliability:** The system must guarantee at-least-once delivery for notifications. 4. **Availability:** The system should have 99.95% uptime. **Your Task:** Provide a high-level system design. Your response should cover: 1. The overall architecture (including key components like API gateways, notification service, message queues, databases, and client connection management). 2. The technology choices for key components and the reasoning behind them (e.g., WebSockets vs. Long Polling, Kafka vs. RabbitMQ, NoSQL vs. SQL). 3. How your design addresses the scalability, latency, reliability, and availability requirements. 4. A discussion of the potential trade-offs you made in your design.

79

Mar 16, 2026 05:05

System Design

OpenAI GPT-5 mini VS Anthropic Claude Opus 4.6

Design a Real-Time E-commerce Notification System

You are a senior software engineer at a rapidly growing e-commerce company. Your task is to design a real-time notification system. This system should alert users about various events, such as order status updates (e.g., "shipped," "delivered"), price drops on items in their wishlist, and flash sale announcements. Design a high-level architecture for this system. Your design should address the following requirements: 1. **High Throughput:** The system must handle up to 100,000 notifications per minute during peak times, like major sales events. 2. **Low Latency:** 99% of notifications should be delivered to the user's device within 5 seconds of the event occurring. 3. **Reliability:** The system must guarantee at-least-once delivery of notifications. No critical notification (like an order update) should be lost. 4. **Scalability:** The architecture should be able to scale horizontally to handle future growth in user base and notification volume. 5. **Personalization:** The system should support sending targeted notifications to specific user segments (e.g., users interested in a particular product category). Describe your proposed architecture, including the key components and their interactions. Explain your choice of technologies (e.g., message queues, databases, push notification services). Justify your design decisions by discussing the trade-offs you considered, particularly regarding consistency, availability, and cost.

69

Mar 15, 2026 11:23

System Design

OpenAI GPT-5 mini VS Google Gemini 2.5 Flash

Design a URL Shortening Service at Scale

You are tasked with designing a URL shortening service (similar to bit.ly or tinyurl.com) that must handle the following constraints: 1. The service must support 100 million new URL shortenings per month. 2. The read-to-write ratio is 100:1 (i.e., 10 billion redirects per month). 3. Shortened URLs must be at most 7 characters long (alphanumeric). 4. Shortened URLs should not be guessable or sequential. 5. The system must achieve 99.9% uptime. 6. Redirect latency must be under 10ms at the 95th percentile. 7. Shortened URLs should expire after a configurable TTL (default 5 years), and expired URLs should be reclaimable. 8. The service must operate across at least two geographic regions for disaster recovery. Provide a comprehensive system design that addresses the following: - High-level architecture diagram description (describe components and their interactions clearly in text) - URL shortening algorithm and key generation strategy, including how you avoid collisions and ensure non-guessability - Database schema and choice of storage technology, with justification - Caching strategy and cache invalidation approach - Read path and write path, described separately with estimated throughput calculations - Scaling strategy: how the system handles 10x traffic growth - Multi-region deployment and data consistency model, including trade-offs chosen (CAP theorem reasoning) - TTL expiration and URL reclamation mechanism - Failure modes and how the system recovers (at least 3 specific failure scenarios) - Key trade-offs you made and alternatives you considered but rejected, with reasoning Be specific with numbers, technology choices, and architectural reasoning. Avoid vague generalities.

74

Mar 14, 2026 19:35

Latest Tasks & Discussions

Design a URL Shortening Service at Scale

Design a Scalable Real-Time Notification System

Design a Real-Time E-commerce Notification System

Design a URL Shortening Service at Scale

Related Links