Introduction

The rifasvelez-web project recently underwent a significant architectural shift with its "V2" update. This overhaul wasn't just about new features; it was a fundamental re-evaluation of how we build and maintain our application, ensuring it remains robust and adaptable for future growth. The core of this modernization involved adopting Hexagonal Architecture to separate concerns and enhance modularity.

The Problem

In many evolving web applications, initial rapid

As web applications evolve, the need for new features like managing "new raffles" becomes paramount. The rifasvelez-web project recently saw an update to facilitate this, specifically targeting the /sorteos route. The core challenge here isn't just to build the feature, but to integrate it in a way that remains scalable, testable, and maintainable without turning the codebase into a tangled mess.

Introducing new features into an existing web application can often be a complex dance between frontend presentation, business logic, and data persistence. In our recent work on the rifasvelez-web project, we tackled this challenge by enhancing our raffle management system to support new raffles, focusing on maintainability and scalability through a well-defined architecture.

The Situation: Expanding Raffle Capabilities

Our rifasvelez-web application needed to evolve beyond its

In the rifasvelez-web project, our focus is on delivering a robust and maintainable web platform. Recently, a significant milestone was reached with the integration of V2 updates, fundamentally driven by an architectural shift towards Hexagonal Architecture. This upgrade was more than just a feature release; it was a strategic move to enhance the system's resilience and adaptability.

The Symptoms

As rifasvelez-web grew, we started noticing common challenges associated with tightly