Understanding Clean Architecture

Before we start building we need to understand what exactly clean architecture is. To understand what clean architecture is lets consider the below scenario:

    Imagine you visit a hospital for treatment.

    Do you walk straight to the lab technician or the pharmacy counter?

    Of course not.

    The typical flow looks like this:

    You (the patient) → Reception → Doctor → (maybe) Lab → (maybe) Pharmacy

    

    Each person/role has a single and clear responsibility. Crucially: if the pharmacy upgrades its billing software, switches suppliers, or is temporarily closed for renovation - the doctor's job remains exactly the same.

That stability is the core idea of Clean Architecture.

Just like the doctor's diagnostic and treatment logic stays independent of how lab results arrive, they can be given directly to the patient as a hard copy or they can be sent to the doctor as softcopy and so on, or how medicines are billed/dispensed, in Clean Architecture your core business rules and domain model live protected in the center - independent of databases, UI frameworks, external APIs, or any other delivery mechanisms

Clean Architecture Model

Hope you got an idea of what Clean Architecture is in the next sections we will discuss what are the problems of Bad Architecture and how Clean Architecture solves them.