Documenting code, one commit at a time.
In our work on the SBSofiaBartoli/crm-saas-backend project, we recently reached a significant milestone in our data architecture. We decided to pivot away from traditional update-heavy CRUD operations, favoring an immutable approach to record management.
In our initial implementation, we treated records as mutable entities. Any change meant performing an
Building a SaaS application often feels like trying to organize a junk drawer: everything is important, but nothing is in the right place. Recently, while working on the crm-saas-backend project, I focused on implementing a robust CRUD lifecycle for client tracking—a feature that could easily become a maintenance nightmare if not properly decoupled from the persistence layer.
In the crm-saas-backend project, our dashboard performance was suffering due to N+1 network requests. To display high-level metrics, the client-side application had to fire multiple separate API calls to various resources, leading to increased latency and unnecessary overhead for the user.
As our SaaS platform grew, the cost of these individual requests
