Implementing Clean Architecture Supported by Structure
•Download as PPTX, PDF•
0 likes•13 views
Has implementing Clean Architecture become more of an ideal than a reality in your projects? Despite its clear rules and intended separations, the complexity of growing codebases and the crunch of time often render these principles invisible in practice. When projects technically fail, the culprit is frequently uncontrolled complexity – where Clean Architecture remains a concept on paper, not in code. In this session, I will show how to get predictability by implementing Clean Architecture through structure, rather than relying on discipline and code reviews only. I’ll show how to create a structure that makes it easy to write the code that follows your architecture and at the same time it makes it difficult to write the code that doesn’t. You will walk away with a recipe and building blocks for creating a foundation in code that sustains Clean Architecture and the level of quality in your code that can control the complexity of the project. This structure will enforce separation of concerns and how dependencies are created. It will deliver predictability by creating a Code Design that is maintainable, extensible and reusable.
Recommended
More Related Content
Similar to Implementing Clean Architecture Supported by Structure
Similar to Implementing Clean Architecture Supported by Structure (20)
Recently uploaded
Recently uploaded (20)
Implementing Clean Architecture Supported by Structure
- 1. onCodeDesign.com/implementing-clean-architecture Drive predictability through Software Design PeakIT - Brașov, 2024 Florin Coroș florin@onCodeDesign.com linkedin.com/in/florincoros Implementing Clean Architecture
- 2. onCodeDesign.com/implementing-clean-architecture Drive predictability through Software Design oncodedesign.com/implementing-clean-architecture Software Architect Consultant Technical Trainer Founder of Code Design enjoing playing GO enjoing traveling Florin Coroș
- 3. onCodeDesign.com/implementing-clean-architecture Drive predictability through Software Design PeakIT - Brașov, 2024 Florin Coroș florin@onCodeDesign.com linkedin.com/in/florincoros Implementing Clean Architecture
- 4. onCodeDesign.com/implementing-clean-architecture Why is Architecture Important -- Robert C. Martin, Clean Architecture The goal of software architecture is to minimize the human resources required to build and maintain the required system
- 5. onCodeDesign.com/implementing-clean-architecture Decompose - Separation of Concerns Title Title Title Title Title Title Title
- 6. onCodeDesign.com/implementing-clean-architecture Manage the Complexity and Size when projects do fail for reasons that are primarily technical, the reason is often uncontrolled complexity
- 7. onCodeDesign.com/implementing-clean-architecture The Architecture is Separation of Concerns and a Set of Rules External Interfaces UI Frameworks Devices Controllers Entities Entities Use Cases
- 8. onCodeDesign.com/implementing-clean-architecture Implementing the Architecture External Interfaces UI Frameworks Devices Controllers Entities Entities Use Cases
- 9. onCodeDesign.com/implementing-clean-architecture Structure that Supports the Architecture External Interfaces UI Frameworks Devices Controllers Entities Entities Use Cases
- 10. Clean Architecture External Interfaces UI Frameworks Devices Controllers Entities Entities Use Cases http://blog.8thlight.com/uncle-bob/2012/08/13/the-clean-architecture.html Presenter Controller UseCase Implementation Presenter Controller UseCase Implementation UseCase InputAbstraction UseCase OutputAbstraction Dependencies should be in one direction only Source code dependencies can only point inwards
- 11. onCodeDesign.com/implementing-clean-architecture Implementing Clean Architecture through Structure • Hide external frameworks to enforce the way they are used • Use assemblies and references among them to enforce rules • Enforce Constructor Dependency Injection that encourages Programming Against Interfaces Create a structure that makes it difficult to write bad code and it makes it easy to write good code, code that follows the architecture and the design
- 12. onCodeDesign.com/implementing-clean-architecture <<interface>> ILogger +LogError() Logger +LogError() Creating a Structure for Clean Architecture External Interfaces UI Frameworks Devices Controllers Entities Entities Use Cases <<public interface>> ILogger +LogError() <<Internal class>> Logger +LogError()
- 13. onCodeDesign.com/implementing-clean-architecture Hide External Libraries from App Code <<Internal class>> Exception Wrappers <<public Interface>> API Interfaces <<Internal class>> Decorators
- 14. onCodeDesign.com/implementing-clean-architecture <<Interface>> TDataModel IRepository +GetEntities<TDataModel>() <<Interface>> TDataModel IUnitOfWork +GetEntities<TDataModel>() +SaveChanges() Database EfRepository EfUnitOfWork <<Stereotype>> <<DTO>> Order <<DTO>> Person Enforce Separation of Data Access Concerns iQuarcDataAccess
- 15. onCodeDesign.com/implementing-clean-architecture DIP to Enforce Separation of Data Access Concern <<Interface>> IDbContextFactory +CreateContext() Database <<DTO>> Customer <<DTO>> Order <<DTO>> Person UnitOfWork Repository DbContextFactory <<Interface>> TDataModel IRepository, IUnitOfWork +GetEntities() +SaveEntities()
- 16. onCodeDesign.com/implementing-clean-architecture <<Attribute>> ServiceAttribute +ServiceAttribute(interface : Type ) IBootstrapper +Run() <<Internal>> DependencyContainerAdapter iQuarcAppBoot AppBoot Hides the DI Framework under Abstractions public interface IPriceCalculator { int CalculateTaxes(Order o, Customer c); int CalculateDiscount(Order o, Customer c); } [Service(typeof(IPriceCalculator), Lifetime.Instance)] interal class PriceCalculator : IPriceCalculator { public int CalculateTaxes(Order o, Customer c) { return 10; // do actual calculation } public int CalculateDiscount(Order o, Customer c) { return 20; // do actual calculation } }
- 17. onCodeDesign.com/implementing-clean-architecture AppBoot: DI Abstractions & Type Discovery <<Interface>> IDbContextFactory +CreateContext() Database <<DTO>> Customer <<DTO>> Order <<DTO>> Person UnitOfWork Repository DbContextFactory <<Interface>> TDataModel IRepository, IUnitOfWork +GetEntities() +SaveEntities() <<Attribute>> ServiceAttribute
- 18. onCodeDesign.com/implementing-clean-architecture Patterns on how most of the code is written [Service(typeof (IOrderingService))] private class OrderingService : IOrderingService { private readonly IRepository repository; private readonly IPriceCalculator calculator; private readonly IApprovalService orderApproval; public OrderingService(IRepository repository, IPriceCalculator calculator, IApprovalService orderApproval) { this.repository = repository; this.calculator = calculator; this.orderApproval = orderApproval; } public SalesOrderInfo[] GetOrdersInfo(string customerName) { var orders = repository.GetEntities<SalesOrderHeader>() ... return orders.ToArray(); } public SalesOrderResult PlaceOrder(string customerName, OrderRequest request) { ... } }
- 20. onCodeDesign.com/implementing-clean-architecture /iQuarc Implementing Clean Architecture through Structure External Interfaces UI Frameworks Devices Controllers Entities Entities Use Cases <<Attribute>> <<Attribute>> ServiceAttribute RepositoryImpl + GetEntities<T>() : IQueriable() + SaveChanges() Hide external frameworks to enforce the way they are used Use assemblies and references among them to enforce rules Enforce Constructor Dependency Injection that encourages Programming Against Interfaces /iQuarc
- 21. onCodeDesign.com/implementing-clean-architecture Drive predictability through Software Design Implementing Clean Architecture PeakIT - Brașov, 2024 florin@onCodeDesign.com linkedin.com/in/florincoros oncodedesing.com/training oncodedesing.com/implementing-clean- architecture calendly.com/florin-oncodedesign/short-call Florin Coroș Software Architect Consultant Technical Trainer