Discover and read the best of Twitter Threads about #cleanarchitecture
Most recents (3)
Clean architecture aka ports and adapters is simply an approach to building systems that follow DIP. That is, depend on abstractions not implementations, and make sure those abstractions don’t depend on details.
#dotnet #cleanarchitecture
#dotnet #cleanarchitecture
It doesn’t make exceptions for different kinds of implementations. It doesn’t exclude web services or email sending or file system access. Why would it be inconsistent about persistence or ORM usage?
If you find it useful to bypass using an abstraction (you control) in favor of relying directly on an implementation detail, go ahead and do so! Your app will still work! But the first law of architecture is everything is a trade off so just understand the pros and cons.
1/ Do I need tool independence?
> The capability of swapping technologies is important for the product roadmap.
Databases, APIs, Messaging Systems...
> The capability of swapping technologies is important for the product roadmap.
Databases, APIs, Messaging Systems...
2/ Do I value Test in Isolation?
> Testing and Test in isolation from its eventual
run-time devices are essential.
> Testing and Test in isolation from its eventual
run-time devices are essential.
5 tips that will improve the design and quality of your #software:
1. Write shorter functions (methods) that do just one thing ("single responsibility principle").
2. Decrease the number of decision points (aka "cyclomatic complexity") per unit (function, method, etc).
...
1. Write shorter functions (methods) that do just one thing ("single responsibility principle").
2. Decrease the number of decision points (aka "cyclomatic complexity") per unit (function, method, etc).
...
...
3. Avoid duplication at all cost!
4. Keep your interfaces small (e.g. the number of arguments a function or class receives).
5. Separate concerns by making your code more modular.
3. Avoid duplication at all cost!
4. Keep your interfaces small (e.g. the number of arguments a function or class receives).
5. Separate concerns by making your code more modular.
What have all these tips in common?
They lead to more robust and moldable software:
1. Components become more loosely coupled and are therefor easier to reuse, test and extend (support new use cases).
...
They lead to more robust and moldable software:
1. Components become more loosely coupled and are therefor easier to reuse, test and extend (support new use cases).
...
