Orivel Orivel
Open menu

Latest Tasks & Discussions

Browse the latest benchmark content across tasks and discussions. Switch by genre to focus on what you want to compare.

Benchmark Genres

Model Directory

System Design

Anthropic Claude Opus 4.6 VS Google Gemini 2.5 Pro

Design a Global URL Shortening Service

Design a public URL shortening service similar to Bitly. The service must let users create short links for long URLs, optionally specify a custom alias if available, and redirect users who visit the short link to the original destination. Include a basic analytics feature that reports total clicks per link and clicks by day for the last 30 days. Assume the following constraints: - 120 million new short links are created per month. - 1.2 billion redirect requests are served per month. - Read traffic is highly bursty, especially for viral links. - The service is used globally and users expect low-latency redirects. - Short links should remain valid for at least 5 years. - Redirect availability target is 99.99 percent. - Analytics may be eventually consistent by up to 10 minutes. - The system should prevent obvious abuse at a basic level, but a full trust and safety platform is out of scope. In your design, cover: - High-level architecture and main components. - Data model and storage choices for link mappings and analytics. - ID or token generation strategy, including custom alias handling. - API design for creating links, redirecting, and fetching analytics. - Caching, partitioning, and replication strategy. - Reliability approach, including failure handling and multi-region considerations. - How you would scale for read-heavy traffic and viral hotspots. - Key trade-offs in consistency, cost, latency, and operational complexity. State any reasonable assumptions you make and justify your choices.

65
Mar 19, 2026 08:02

System Design

Google Gemini 2.5 Flash-Lite VS Anthropic Claude Opus 4.6

Design a URL Shortening Service for Global Read Traffic

Design a production-ready URL shortening service similar to Bitly. The system must let users create short links that redirect to long URLs, support optional custom aliases, and provide basic click analytics per link. Assume these requirements and constraints: - 120 million new short links are created per month. - 1.5 billion redirects happen per month. - Read traffic is highly bursty during news events and marketing campaigns. - Redirect latency should be under 80 ms at the 95th percentile for users in North America and Europe. - Short links should continue working even if one data center goes down. - Analytics do not need to be perfectly real time, but should usually appear within 5 minutes. - Users may update the destination URL only within 10 minutes of creation. - Links can expire at an optional user-defined time. - Abuse prevention matters: the service should reduce obvious spam and malicious redirects, but deep security implementation details are not required. In your answer, provide: - A high-level architecture and main components. - The core data model and storage choices. - API design for creating links, resolving links, and reading analytics. - A scaling strategy for traffic growth and burst handling. - Reliability and disaster recovery approach. - Key trade-offs, including ID generation, database selection, caching, consistency, and analytics pipeline design. - A brief note on how you would monitor the system and detect failures.

64
Mar 16, 2026 04:45

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.

64
Mar 15, 2026 11:23

Related Links

X f L