DEV Community

Part 1: What is Clean Architecture?

mohamed Tayel on July 03, 2024

Understanding Clean Architecture I would like to express my gratitude to Gill Cleeren, Pluralsight Author, for his excellent course on A...

Read full post

Antonio | CEO at Litlyx.com • Jul 4

MVVM, Clean architeture is a standard for very large and complex code bases that need a structure. I used when i was a enloyee in a big company. I rember that the barrier was really big for a person who is not a "at his prime" so sometimes scares the people. But is the optimal solution for large scale codebases.
Good work.
Antonio, CEO at Litlyx

mohamed Tayel • Jul 5

thanks

Michal Kunikowski • Jul 7

There is also hexagon architecture. Maybe you can compere.
I can add one article for reference (sorry for medium)

"Hexagonal Architecture, there are always two sides to every story"
medium.com/ssense-tech/hexagonal-a...

jmgarridopaz.github.io/content/art...

HlexNC • Jul 5

Can you next time provide an example of project with clean architecture? Thanks.

mohamed Tayel • Jul 5

soon

mohamed Tayel • Aug 26

example using .net core API
github.com/mohamedtayel1980/clean-...

Navin Yadav • Sep 1

Ali Nour Al Din • Jul 9

منور يا هندسة💕

James McMenamin • Jul 6

For mobile and large codebase I have switched to a Vertical architecture + clean design approach nowadays just easier to manage the base.

Nehemiah Jeyakumar • Jul 4

Great article

mohamed Tayel • Jul 5

thanks

Comment hidden by post author - thread only accessible via permalink

z2lai • Jul 3 • Edited

Your diagram looks more like rectangles instead of circles 😀. I've always wondered, is there an actual difference in what the circlular clean architecture diagrams depict vs the non-circular diagrams?

FYI, if your article was assisted by AI, you should disclose that or tag it appropriately.
dev.to/devteam/guidelines-for-ai-a...

Top Developers • Aug 29

Thanks for this great article but I have some questions that need to clarify.

1- Entities: Represent the core business objects of the application. They encapsulate the most general and high-level rules. They are typically rich domain objects containing business rules and logic.
I believe entities shouldn't have any business logic and if you need to have some validation rules we can keep it in use cases or in a helper class to validate data before saving, is that right ?

2- User interface: Include the UI, database, web frameworks, and any other external tools or delivery mechanisms. These are the outermost layer and have the least amount of code.
the user interface layer is just part of the framework & drivers layer and this layer includes (DB - Devices - Web - UI - External Interfaces).

Marcelloh • Jul 5

How would a business rule be applied on an entity-field (if the only way is in)?

mohamed Tayel • Jul 5

Let's say we have an entity called order and i want make sure when set quantity it must >0 we will do the following
public class Order
{
public int Quantity { get; private set; }

public void SetQuantity(int quantity)
{
    if (quantity <= 0)
    {
        throw new ArgumentException("Quantity must be greater than zero.");
    }
    Quantity = quantity;
}

}
as you see the i make private set and create method for validate the quantity
This encapsulates the business rule within the entity, making it easier to maintain and understand

Marcelloh • Jul 6

In that case, the business rule is "hidden" in the entity, which is not in the Application Core.

mohamed Tayel • Jul 7

sorry, I misunderstood your question. To clarify, we can add business rule in APP core

public interface IOrderService
{
void SetOrderQuantity(Order order, int quantity);
}

// Application Core - Service Implementation
public class OrderService : IOrderService
{
public void SetOrderQuantity(Order order, int quantity)
{
if (quantity <= 0)
{
throw new ArgumentException("Quantity must be greater than zero.");
}
order.SetQuantity(quantity);
}
}

Adesoji1 • Jul 4

This is rich

mohamed Tayel • Jul 4

thanks

Some comments have been hidden by the post's author - find out more