> For the complete documentation index, see [llms.txt](https://guilhermesantos.gitbook.io/niro-health/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guilhermesantos.gitbook.io/niro-health/the-mission/simplified-dissociation.md).

# Simplified Dissociation

Abstraction based on Clean Architecture and S.O.L.I.D

You have surely been in a situation where your database was strictly coupled to your entity, and because of this you were unable to change your database to another type of technology, am I right? - I know this sounds familiar, because we have all experienced this at some point.

{% hint style="info" %}
Within Niro's architecture we have an intelligent separation between layers, to dynamically segment each part of our application.
{% endhint %}

### But does that make development take longer?

Abstracting your architecture can take more time in development, but since you are using a framework (Niro), you will have several examples and even a command to generate an entity, and this entity will already have the routes, forming a CRUD (Create, Read, Update, Delete), you will not spend more than a few hours to understand how the implementation works.