Separation of concerns in LLD - System Design Guide

Problem Statement

When different parts of a program handle multiple responsibilities mixed together, it becomes hard to understand, maintain, and update. Changes in one part can unexpectedly break others, causing bugs and slowing development.

Solution

Separate the program into distinct sections, each handling a single responsibility or concern. This way, each part can be developed, tested, and changed independently without affecting others.

Architecture

┌───────────────┐     ┌───────────────┐     ┌───────────────┐
│ User Interface│────▶│ Business Logic│────▶│ Data Access   │
└───────────────┘     └───────────────┘     └───────────────┘

This diagram shows three separate layers: User Interface, Business Logic, and Data Access, each focusing on a specific concern.

Trade-offs

✓ Pros

→

Improves code readability by organizing code into clear sections.

→

Makes testing easier by isolating functionality.

→

Facilitates parallel development by different teams.

→

Reduces risk of bugs when changing one part.

✗ Cons

→

Initial design takes more time to plan and implement.

→

May introduce extra layers that add slight performance overhead.

→

Requires discipline to maintain clear boundaries.

Use when building medium to large applications where maintainability and scalability are important.

Avoid for very small scripts or prototypes where simplicity and speed are more important than structure.

Real World Examples

Amazon

Amazon separates its web interface, order processing logic, and database access to allow independent updates and scaling.

Netflix

Netflix uses separation of concerns to isolate streaming UI, recommendation algorithms, and data storage for better maintainability.

Uber

Uber separates rider app UI, trip management logic, and payment processing to handle complex workflows cleanly.

Code Example

The before code mixes validation, payment, and database logic in one class, making it hard to maintain. The after code separates these concerns into different classes, so each part can be changed independently.

LLD

### Before: No separation of concerns
class OrderProcessor:
    def process_order(self, order):
        print(f"Validating order {order}")
        # validation logic
        print(f"Charging payment for {order}")
        # payment logic
        print(f"Saving order {order} to database")
        # database logic

### After: Separation of concerns
class OrderValidator:
    def validate(self, order):
        print(f"Validating order {order}")
        # validation logic

class PaymentProcessor:
    def charge(self, order):
        print(f"Charging payment for {order}")
        # payment logic

class OrderRepository:
    def save(self, order):
        print(f"Saving order {order} to database")
        # database logic

class OrderProcessor:
    def __init__(self):
        self.validator = OrderValidator()
        self.payment = PaymentProcessor()
        self.repository = OrderRepository()

    def process_order(self, order):
        self.validator.validate(order)
        self.payment.charge(order)
        self.repository.save(order)

Alternatives

Monolithic design

All concerns are mixed in one codebase without clear boundaries.

Use when: Choose when building very simple or small applications where speed of development is critical.

Microservices

Separates concerns at the service level, splitting the system into independent deployable services.

Use when: Choose when the system is large, requires independent scaling, and teams are distributed.

Summary

Separation of concerns divides a system into parts that each handle a specific responsibility.

This makes code easier to understand, maintain, and test by isolating changes.

It is best used in medium to large systems where complexity needs to be managed.

Practice

1. What is the main purpose of separation of concerns in system design?

easy

A. To divide a system into parts that each handle a specific job

B. To combine all system functions into one module

C. To make the system run faster by using fewer parts

D. To remove all interfaces between system components

Solution

1. Step 1: Understand the concept of separation of concerns

   It means dividing a system into parts where each part has a clear, specific responsibility.

2. Step 2: Compare options with the concept

   Only To divide a system into parts that each handle a specific job describes dividing the system into parts with specific jobs, matching the concept.

3. Final Answer:

   To divide a system into parts that each handle a specific job -> Option A

4. Quick Check:

   Separation of concerns = divide system parts [OK]

Hint: Think: separate jobs make systems simpler [OK]

Common Mistakes:

• Confusing separation with combining functions
• Thinking it speeds up system by reducing parts
• Ignoring the role of interfaces

2. Which of the following is the correct way to apply separation of concerns in code structure?

easy

A. Separating UI code, business logic, and data access into different modules

B. Writing all code in one large file for easy access

C. Mixing UI logic and data processing in the same function

D. Ignoring interfaces between different parts

Solution

1. Step 1: Identify proper separation in code

   Separation of concerns means keeping UI, logic, and data handling separate.

2. Step 2: Match options to this principle

   Separating UI code, business logic, and data access into different modules correctly separates these concerns into different modules.

3. Final Answer:

   Separating UI code, business logic, and data access into different modules -> Option A

4. Quick Check:

   Separate UI, logic, data = Separating UI code, business logic, and data access into different modules [OK]

Hint: Keep UI, logic, data in separate files [OK]

Common Mistakes:

• Mixing UI and logic in one place
• Putting all code in one file
• Ignoring module boundaries

3. Consider this simplified code snippet applying separation of concerns:

class DataFetcher:
    def fetch(self):
        return "data"

class Processor:
    def process(self, data):
        return data.upper()

class UI:
    def display(self, processed_data):
        print(processed_data)

fetcher = DataFetcher()
data = fetcher.fetch()
processor = Processor()
processed = processor.process(data)
ui = UI()
ui.display(processed)

What will be printed when this code runs?

medium

A. processor

B. data

C. fetch

D. DATA

Solution

1. Step 1: Trace data flow through classes

   DataFetcher returns "data". Processor converts it to uppercase "DATA". UI prints it.

2. Step 2: Determine final output

   The UI prints the processed data, which is "DATA" in uppercase.

3. Final Answer:

   DATA -> Option D

4. Quick Check:

   Uppercase processed data = DATA [OK]

Hint: Follow data from fetch to display [OK]

Common Mistakes:

• Confusing original data with processed data
• Ignoring the uppercase conversion
• Thinking print shows method names

4. In a system designed with separation of concerns, which issue indicates a violation of this principle?

medium

A. Clear division of responsibilities between components

B. Separate modules for UI and data storage communicating via interfaces

C. A module handling both user input validation and database queries

D. Using interfaces to connect independent parts

Solution

1. Step 1: Identify violation of separation of concerns

   A module doing multiple unrelated jobs breaks the principle.

2. Step 2: Match options to violation

   A module handling both user input validation and database queries shows one module handling both validation and database queries, mixing concerns.

3. Final Answer:

   A module handling both user input validation and database queries -> Option C

4. Quick Check:

   Mixed responsibilities = violation [OK]

Hint: One module, one job only [OK]

Common Mistakes:

• Thinking interfaces cause violation
• Believing clear division is a problem
• Confusing separation with duplication

5. You are designing a web application with separation of concerns. Which design choice best supports this principle while ensuring scalability?

hard

A. Combine UI rendering, business logic, and data access in a single service

B. Use separate services for UI, business logic, and data storage connected via APIs

C. Store all data and logic in the client-side code for faster access

D. Avoid defining clear interfaces between components to reduce complexity

Solution

1. Step 1: Understand separation and scalability needs

   Separation means dividing concerns; scalability means easy to grow and maintain.

2. Step 2: Evaluate design options

   Use separate services for UI, business logic, and data storage connected via APIs uses separate services connected by APIs, which keeps concerns separate and supports scaling.

3. Final Answer:

   Use separate services for UI, business logic, and data storage connected via APIs -> Option B

4. Quick Check:

   Separate services + APIs = scalable separation [OK]

Hint: Separate services with APIs scale best [OK]

Common Mistakes:

• Combining all logic in one service
• Putting logic only on client side
• Skipping interfaces between parts