Clean Architecture implementation

Is it worth it to use Clean Architecture in 2021? I will show you some patterns that can be used efficiently in your applications using this architecture.

Photo by Simone Hutsch on Unsplash

If you are reading these lines, you should probably know about Clean Architecture and you may hesitate when choosing one specific architecture for your whole project.

In this article, I will show you a way to implement Clean Architecture in a recent app and then give you an objective point of view of the pros and cons using this architecture.

Short reminder of Clean Architecture

The idea behind this concept is relatively simple: build a software architecture divided into independent layers in order to isolate the different concerns. By doing this, you can easily test your components and add or remove modules to your code because each layer is independent. Thus, you will also know exactly where to apply changes in your code, which is very appreciated when fixing bugs or updating use cases.

Using the clean architecture, changing a database, a network provider for an API, or even a UI library should be possible by only modifying a few already-known files. Thanks to dependency inversion and composition over…