Container/Presenter Pattern — Separate Logic from Display

In this tutorial, you'll learn how the Container/Presenter pattern separates stateful logic (containers) from display (presenters).

What You'll Learn

how the Container/Presenter pattern separates stateful logic (containers) from display (presenters).

Why It Matters

Components mixing logic and display are hard to test and reuse. Separation enables both.

Real-World Use

React smart/dumb component pattern, Redux containers, and Angular smart components.

The Container/Presenter Pattern

The Container/Presenter pattern addresses a specific recurring design problem by providing a reusable solution structure. Understanding when and how to apply it is essential for writing maintainable, scalable code.

Key Concepts

• Abstraction: Container/Presenter provides clean separation between interface and implementation.
• Reusability: Pattern can be applied across different contexts.
• Maintainability: Code organized with Container/Presenter is easier to understand.
• Testability: Components can be tested in isolation.

Structure

The following diagram shows the structure of this pattern:

classDiagram
    class ContainerPresenter {
        +operation()
    }
    class Implementation {
        +execute()
    }
    ContainerPresenter --> Implementation

Implementation

import React, { createContext, useContext, useState } from 'react';

const ContainerPresenterContext = createContext();

export function ContainerPresenterProvider({ children }) {
    const [state, setState] = useState({});

    const value = {
        state,
        update: (key, data) => setState(prev => ({...prev, [key]: data})),
        get: (key) => state[key],
    };

    return (
        <ContainerPresenterContext.Provider value={value}>
            {children}
        </ContainerPresenterContext.Provider>
    );
}

export function useContainerPresenter() {
    const context = useContext(ContainerPresenterContext);
    if (!context) throw new Error('useContainerPresenter must be inside ContainerPresenterProvider');
    return context;
}

// Usage:
// function Profile() {
//   const { state, update } = useContainerPresenter();
//   return <div>{state.user?.name}</div>;
// }

Expected output:

// (JSX renders UI - output depends on component tree)

Key Participants

• Client: Code that uses the Container/Presenter.
• Container/Presenter: The main abstraction provided by the pattern.
• Implementation: Concrete realization of the pattern.
• Data/State: Information managed by the pattern.

Real-World Examples

• DodaTech uses this pattern internally for consistent cross-cutting concerns.
• Major frameworks and libraries implement this pattern as a core architectural element.
• Production systems at scale depend on this pattern for reliability.

Related Patterns

• Mvc Ui

• Mvvm Pattern

• Redux

• Design Patterns — the complete patterns catalog.

Pros and Cons

Common Mistakes

1. **Over-engineering: Applying Container/Presenter where a simpler solution suffices, adding unnecessary complexity.

2. **Wrong granularity: Implementing Container/Presenter at the wrong level of abstraction.

3. **Thread Safety ignored: Using Container/Presenter in concurrent context without proper synchronization.

4. **Tight coupling: Violating the pattern intent by creating hidden dependencies.

5. **Premature optimization: Introducing Container/Presenter before there is evidence it is needed.

Practice Questions

1. What problem does the Container/Presenter pattern solve? Describe a real-world scenario where using it improves code quality.

2. How does Container/Presenter differ from alternative approaches? What are the trade-offs?

3. What testing Strategy would you use for code that implements Container/Presenter?

4. How would you refactor legacy code to introduce Container/Presenter?

5. When should you NOT use Container/Presenter? Describe scenarios where it adds unnecessary complexity.

Challenge

Implement a complete Container/Presenter example in Python with unit tests. Include error handling, edge cases (empty data, null values, concurrent access), and a performance comparison against a simpler alternative. Document your design decisions.

Real-World Task

Find a section of code in your current project that could benefit from the Container/Presenter pattern. Refactor it, write tests, and measure the improvement in testability, coupling, and cohesion.

Security Tip: When implementing Container/Presenter, ensure proper input validation, avoid exposing internal state, and follow Least Privilege. At DodaTech, all implementations undergo security review.

Built by the developers of Doda Browser, DodaZIP, and Durga Antivirus Pro.