YAGNI (You Aren't Gonna Need It) in LLD - Scalability & System Analysis

Scalability Analysis - YAGNI (You Aren't Gonna Need It)

Growth Table: YAGNI in System Design

Users	System Complexity	Features Implemented	Infrastructure	Maintenance Effort
100 users	Simple, minimal features	Only core features needed	Single server, basic DB	Low
10,000 users	Moderate complexity, some optimizations	Essential features only, no premature additions	Load balancer, DB replicas	Moderate
1,000,000 users	High complexity, optimized for scale	Features added based on real need	Multiple servers, caching, sharding	High but manageable
100,000,000 users	Very high complexity, mature system	Only proven features, no unused code	Distributed systems, CDNs, microservices	Very high, requires automation

First Bottleneck: Over-Engineering and Unused Features

When YAGNI is ignored, the first bottleneck is the system complexity itself. Adding features before they are needed causes:

• Slower development and deployment
• Harder to maintain and debug code
• Increased resource usage without benefit

This complexity slows down the team and system performance before user scale becomes a problem.

Scaling Solutions with YAGNI in Mind

• Start Simple: Build only what is necessary for current users.
• Iterative Development: Add features based on real user feedback and data.
• Modular Design: Design components so they can be extended later without major rewrites.
• Refactoring: Regularly clean up code to remove unused parts.
• Automated Testing: Ensure new features don't break existing functionality.
• Monitor Usage: Track which features are used to decide what to keep or remove.

Back-of-Envelope Cost Analysis

By following YAGNI:

• Development time is reduced by avoiding unnecessary features.
• Maintenance costs stay low due to simpler codebase.
• Infrastructure costs are optimized since only needed features consume resources.
• Example: For 10,000 users, building only core features might require 2 servers and 1 DB replica, costing less than a complex system with many unused features.

Interview Tip: Structuring YAGNI Discussion

When asked about scalability and YAGNI, structure your answer as:

1. Explain YAGNI: Emphasize building only what is needed now.
2. Identify Risks: Discuss how premature features add complexity and slow scaling.
3. Scaling Impact: Show how simpler systems scale better initially.
4. Solutions: Talk about iterative development and modular design.
5. Real-World Example: Share a scenario where avoiding unnecessary features helped scale efficiently.

Self-Check Question

Your database handles 1000 QPS. Traffic grows 10x. What do you do first?

Answer: Before scaling infrastructure, check if all current features are needed. Remove or postpone unused features to reduce load. Then scale database with read replicas or caching as needed.

Key Result

YAGNI helps keep systems simple and scalable by avoiding unnecessary features that add complexity and slow down growth.

Practice

1. What does the YAGNI principle primarily encourage in system design?

easy

A. Build only features you currently need

B. Plan and build all possible future features

C. Add complex layers for scalability upfront

D. Write extra code for potential edge cases

Solution

1. Step 1: Understand YAGNI meaning

   YAGNI stands for "You Aren't Gonna Need It" and advises to avoid building features before they are necessary.

2. Step 2: Match principle to options

   Build only features you currently need matches the idea of building only what is needed now, while others suggest building for future or complexity.

3. Final Answer:

   Build only features you currently need -> Option A

4. Quick Check:

   YAGNI = Build only what you need now [OK]

Hint: YAGNI means avoid future guesswork, build now only [OK]

Common Mistakes:

• Thinking YAGNI means planning for all future needs
• Confusing YAGNI with over-engineering
• Assuming YAGNI discourages any planning

2. Which of the following is the correct way to apply YAGNI when designing a new feature in a system?

easy

A. Add detailed logging for every possible error before deployment

B. Design the database schema to handle all future data types

C. Write unit tests for features you plan to add later

D. Implement only the core functionality needed for the feature now

Solution

1. Step 1: Identify core YAGNI practice

   YAGNI advises to implement only what is necessary now, avoiding premature additions.

2. Step 2: Evaluate options for current need focus

   Implement only the core functionality needed for the feature now focuses on core functionality now, while others add future or unnecessary work.

3. Final Answer:

   Implement only the core functionality needed for the feature now -> Option D

4. Quick Check:

   YAGNI = Build core now, skip extras [OK]

Hint: Focus on core feature first, skip extras [OK]

Common Mistakes:

• Adding features or tests for future needs
• Over-engineering database for unknown data
• Writing unnecessary logs before real errors occur

3. Consider this scenario: A team adds a caching layer anticipating high traffic, but the system never reaches that load. What does this violate in terms of YAGNI?

medium

A. They avoided unnecessary complexity

B. They followed YAGNI by preparing for future needs

C. They built a feature they didn't need yet

D. They simplified the system by adding cache

Solution

1. Step 1: Analyze the caching layer addition

   The team added caching before it was needed, anticipating future load.

2. Step 2: Relate to YAGNI principle

   YAGNI discourages building features before they are actually needed, so this is a violation.

3. Final Answer:

   They built a feature they didn't need yet -> Option C

4. Quick Check:

   YAGNI violation = building unneeded features [OK]

Hint: Building features before need breaks YAGNI [OK]

Common Mistakes:

• Thinking preparing for future is YAGNI
• Confusing simplification with premature optimization
• Assuming caching always simplifies system

4. A developer added a complex permission system anticipating many user roles, but the product currently has only one role. What is the main issue here related to YAGNI?

medium

A. The developer ignored YAGNI by adding unnecessary complexity

B. The permission system is too simple for current needs

C. The system is scalable and follows YAGNI

D. The product requires multiple roles immediately

Solution

1. Step 1: Identify the developer's action

   The developer added a complex system for roles not currently needed.

2. Step 2: Connect to YAGNI principle

   YAGNI advises against adding complexity before it's necessary, so this is a violation.

3. Final Answer:

   The developer ignored YAGNI by adding unnecessary complexity -> Option A

4. Quick Check:

   Unneeded complexity violates YAGNI [OK]

Hint: Avoid complexity until it's truly needed [OK]

Common Mistakes:

• Assuming scalability means following YAGNI
• Believing all future roles must be planned now
• Confusing simple with insufficient

5. You are designing a messaging system. You consider adding encryption support now, but the current users do not require it. According to YAGNI, what should you do?

hard

A. Implement encryption now to avoid future rework

B. Skip encryption for now and add it when users need it

C. Design the system assuming all messages are encrypted

D. Build a complex key management system upfront

Solution

1. Step 1: Understand current user needs

   Users do not require encryption now, so it is not immediately necessary.

2. Step 2: Apply YAGNI principle to design decision

   YAGNI advises to avoid building features before they are needed, so skip encryption now.

3. Final Answer:

   Skip encryption for now and add it when users need it -> Option B

4. Quick Check:

   YAGNI = build features only when needed [OK]

Hint: Add features only when users actually need them [OK]

Common Mistakes:

• Building features just to avoid future work
• Assuming all users need encryption immediately
• Over-engineering system upfront