Download as PDF, PPTX
More Related Content
![[Container Plumbing Days 2023] Why was nerdctl made?](https://cdn.slidesharecdn.com/ss_thumbnails/containerplumbing2023whywasnerdctlmade-230323115340-794fba85-thumbnail.jpg?width=640&height=640&fit=bounds)
![[CB16] Be a Binary Rockstar: An Introduction to Program Analysis with Binary ...](https://cdn.slidesharecdn.com/ss_thumbnails/cb16dantoineen-161109043343-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to Clean architecture with Python
![Attack surfaces and attack tress[inform]](https://cdn.slidesharecdn.com/ss_thumbnails/lecture03-260108015941-a4dee53b-thumbnail.jpg?width=640&height=640&fit=bounds)
Clean architecture with Python
- 1. Blank Slide Jair Vercosa CleanArchitecture with Python https://vercosa.life https://medium/@jairvercosa https://github.com/jairvercosa Made in Brazil
- 2. Carta helps privatecompanies, public companies, and investors manage their cap tables, valuations, investments, and equity plans. On the employee side, the platform provides ways to participate on liquidity events and exercise their stock options. Private, Public, Investors, and beyond! !2
- 3. 1. Concepts 2. Rules 3.Layers 4. Code 5. The Startup Approach Agenda !3
- 4.
- 5. Clean Architecture Universal rulesof software architecture that when applied can dramatically improve developer productivity throughout the life of any software system. What is it?
- 6. !6 Rules High-level components shouldavoid depending on low-level components. The dependency is always inwards! Dependency rule Your system should scream your domain and not a framework architecture. Screaming architecture Your system should scream your domain and not a framework architecture. Database, web, frameworks are all simple details High cohesion and lower coupling in all levels (objects, packages, systems) Cohesion vs Coupling
- 7.
- 8.
- 9.
- 10.
- 11.
- 12.
- 13.
- 14. Entities Encapsulates the Enterprisewide business rules. They are the least likely to change when something external changes. Definition Entities
- 15.
- 16. Use Cases Use Cases Itorchestrates the flow of data to-from entities. It has the application business logic and manages the different entities involved in some operation. Definition Entities
- 17.
- 18. Interface Adapters Responsible fortranslating the data from the database or inputs into the format to be used by the domain. Definition Interfaces Adapters Use Cases Entities
- 19.
- 20. Infrastructure Infrastructure The edges ofthe application, usually where you collect the inputs, deliver the outputs, persist data, and make communication with external systems. Definition Interfaces Adapters Use Cases Entities
- 21.
- 22.
- 23.
- 24. Separation of concerns !24 Welldefined responsibilities for each layer and clear boundaries. Low coupling and high cohesion.
- 25. Better Testing !25 The coreof your business ends at the Use Case level. Therefore you can test with simple Python objects. The dependency rule helps you to implement interfaces for testing.
- 26. Flexibility !26 The lower yourlayer, the easier becomes to replace layers. Depending on abstract/interfaces makes your code way easier to work with.
- 27.
- 28. Embrace the framework,but act as it wasn’t there * Use interfaces/abstraction as much as you can * Create an interface for queries, even if your ORM is nice. Specially if your ORM is nice!! * Always have an Use Case layer for business logic
- 29. Build independent modules *Your modules should care about only one thing. But it doesn’t mean only one model. * Avoid foreign keys between modules * Aways create a service layer for communication between modules
- 30. Delegate responsibilities! Butdon’t blindly trust it! * Adapters! Adapters! Adapters!
- 31. Always revisit yourcode Startup is about prototyping, testing, validating, failing, iterate! Don’t forget to iterate over your code again!!!
- 32.
- 33.
- 34.
- 35.