Imagine deploying a new feature, only to find your application struggling under the load. That's what happened when we integrated a new mailing service into our FNSM portal backend.

This is the story of how we refactored a seemingly simple feature to handle increased load and ensure maintainability.

The Initial Implementation

Our initial approach was straightforward: when a business

Introduction

The FNSM-2026-PORTAL/FNSM-Portal-Frontend project focuses on developing the user interface for the FNSM portal. Recent work has concentrated on refining the location picker component and eliminating hardcoded values to enhance flexibility and accuracy.

The Challenge

The initial implementation of the location picker suffered from a bug that affected its accuracy.

The FNSM-2026-PORTAL/FNSM-Portal-Backend project is undergoing changes to centralize and streamline routing configurations. This enhancement aims to improve maintainability and scalability of the application by consolidating route definitions.

The Problem: Scattered Route Definitions

Previously, route definitions might have been spread across different modules or files, making it difficult

Introduction

We've been working on the backend for our FNSM Portal, focusing on solidifying the business logic layer. A key part of this has involved defining robust Data Transfer Objects (DTOs) and implementing validation using Zod. This ensures data consistency and reduces errors throughout the application.

Business Model and DTOs

Our approach begins with a well-defined business model