You're reading from Clean Architecture with Python Implement scalable and maintainable applications using proven architectural principles

Product type Paperback

Published in Jun 2025

Publisher Packt

ISBN-13 9781836642893

Length 362 pages

Edition 1st Edition

Languages

Tools

Gokit

Concepts

Programming Language

Author (1):

Sam Keen

View More author details

Table of Contents (18) Chapters

Preface

1. Part 1: Foundations of Clean Architecture in Python

2. Clean Architecture Essentials: Transforming Python Development FREE CHAPTER

3. SOLID Foundations: Building Robust Python Applications

4. Type-Enhanced Python: Strengthening Clean Architecture

5. Part 2: Implementing Clean Architecture in Python

6. Domain-Driven Design: Crafting the Core Business Logic

7. The Application Layer: Orchestrating Use Cases

8. The Interface Adapters Layer: Controllers and Presenters

9. The Frameworks and Drivers Layer: External Interfaces

10. Implementing Test Patterns with Clean Architecture

11. Part 3: Applying Clean Architecture in Python

12. Adding Web UI: Clean Architecture’s Interface Flexibility

13. Implementing Observability: Monitoring and Verification

14. Legacy to Clean: Refactoring Python for Maintainability

15. Your Clean Architecture Journey: Next Steps

16. Other Books You May Enjoy

17. Index

Enhancing the domain model with aggregates and factories

Having established our core entities, value objects, and domain services, we now turn our attention to more advanced domain concepts. These concepts will help us create a more robust and flexible domain model, further enhancing our Clean Architecture implementation.

DDD patterns

DDD offers several advanced patterns that can help us manage complexity and maintain consistency in our domain model. Let’s explore some of these patterns and how they apply to our task management system.

Aggregates

Aggregates are a crucial pattern in DDD for maintaining consistency and defining transactional boundaries within the domain. An aggregate is a cluster of domain objects that we treat as a single unit for data changes. Each aggregate has a root and a boundary. The root is a single, specific entity contained in the aggregate, and the boundary defines what is inside the aggregate.

In our task management system, a natural...