The Projects

TeleScope is an open source project that contains several assemblies to help you building your software with a clean architecture approach. The assemblies contain often used functionalities like reading and writing files types e.g. CSV or JSON or access to an external infrastructure via MQTT or HTTP. You can easily exend the functions of the provided assemblies by using their interfaces and abstractions.

The binaries are developed with .NET Standard so that every kind of .NET related project can use them. You can integrate the assemblies as NuGet packages, for more information please take a look into the NuGet Gallery. If you want to look into the source code itself, you will find the project on GitHub.

Clean Architecture

The implementation of clean architecture follows the ideals of Uncle Bob and Jason Taylor - so thank you both!

To give you a brief overview how it works, please look at the flow chart below. Each layer represents one or more assemblies in your app. To be clear each box carries the word layer.

Now I will state out some principles for each layer. Please note that this list has not the intention to be complete. So you might consider to check further literature or contact me in case of emergency.

• The entity layer, also known as domain or abstraction layer, holds interfaces, abstractions and implementations that are intended to be used across different applications. These should belong to the same application field. In addition the entities should have no external dependencies.
  In other words:If you or your company has a bunch of applications that maybe interact with each other, it is a good idea to place shared definitions (and in some circumstances the implementations) in this layer.
• The application layer holds all definitions and implementations, that are specific for your awesome application. This layer has only dependencies to the entities and abtractions your need to build your specific business logic. So no entities should be present that you don't use.
• The infrastructure layer provides logic for infrastructure and persistence concerns, so here are multiple similar tasks combined into one logical layer.
  Like the names are revealing, the persistence layer covers all implementations to access your local system like files or databases. The interfaces that are in use here, should come from the entity or application layer.
  The infrastructure implementations are used to access remote services like other web servers, Email or whatsoever. It is recommended to split this outer layer into separate named assemblies, to ensure a high independency when developing or updating these libraries. Working in a team becomes also more clear when you follow that approach.
  
• Last but not least the presentation layer depends on all layers below. This highest layer only plugs things together and ships your UI, so the user can interact with your system. This layer should be the most lightweight one, which is a good idea in the fast moving world of user interfaces.

Conclusion

Now, if you like this way of organizing your software architecture, please take a deeper look into the videos or blog posts of Jason Taylor, because he explains that stuff with lots more details. And if you like to test some ready-to-go assemblies that follow these principles, please download the TeleScope assemblies and use them according to your requirements.

Have a nice day!