Home Projects Portfolio Dashboard Export PDF Log in

Languages

English
210

Latest Updates

Documenting code, one commit at a time.

Maintaining Type Integrity in Hexagonal Architectures

Updating core data schemas is an inevitable part of a growing e-commerce application. Recently, in the admin-ecommerce project, we faced the challenge of realigning our TypeScript type definitions to match updated backend schemas. This task highlighted the importance of strictly maintaining our domain layer boundaries.

The Challenge of Schema Drift

When working with Hexagonal Architecture,

Scaling Admin Interfaces: Implementing Customer Management

Improving Data Management

In the admin-ecommerce project, we recently focused on enhancing our administrative dashboard to provide better oversight of our customer base. As our platform grows, managing user information becomes increasingly complex, necessitating a more robust and scalable approach to data presentation.

The Implementation Strategy

To manage our customer data, we moved

Adopting Immutability: Why We Removed Our Update Endpoints

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.

The Problem with Traditional Updates

In our initial implementation, we treated records as mutable entities. Any change meant performing an

Scaling CRM Logic with Hexagonal Architecture

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.

Optimizing CRM Data Retrieval: Implementing Aggregate Metrics Endpoints

The Bottleneck

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.

The Challenge

As our SaaS platform grew, the cost of these individual requests