Introduction

In the North-South project, managing the lifecycle of payment transactions is critical. A common challenge in complex systems is ensuring that domain objects do not transition into invalid states—such as creating a payment after a transaction has already been cancelled or completed.

The Problem

We identified a potential race condition and logic gap where payment services

In the North-South project, we recently tackled a critical challenge regarding payment frequency adjustments. When a user updates their billing cycle, it often creates discrepancies with previously processed payments. Ensuring that our backend correctly reconciles these changes is vital for maintaining financial accuracy.

The Challenge: Contextual State Shifts

When a payment frequency

Consistency is the bedrock of any payment system. In the North-South project, we recently tackled a challenge involving payment state synchronization after adjusting billing period values. When financial records are recalculated mid-cycle, existing payment entries can quickly become stale, leading to discrepancies between the source of truth and processed transactions.

The Challenge: State

Introduction

In our project project-sass-lopdp, we have been focusing on strengthening our data registration layer. As we scale, maintaining a clean separation between our business logic and our data persistence layer has become a priority. By adopting a Hexagonal Architecture approach, we ensure that our core registration logic remains decoupled from the infrastructure.

Getting Started

I have recently started working on my personal project, the 'portafolio-web-dev'. The goal of this project is to build a high-performance, maintainable showcase for my development work. To achieve this, I have begun setting up the foundational architecture using Astro and the Repository Pattern.

The Power of Astro for Portfolios

When building a portfolio, speed and SEO