Santa Fe — Citizen Services

SANTA FE

Citizen app · TypeScript · Santa Fe

Citizen app for the Santa Fe Municipality, built at Crombie: appointments, fine payment and tracking, property-tax debts and training enrollment, with a backoffice to manage schedulers, procedures and users. My role: end-to-end Full Stack Engineer — I built the core of the app's appointment system.

public sector

Software for government: shifting requirements, legacy systems you can't touch and users of every profile. A school of pragmatism.

MICROSERVICES

integration with municipal systems

A microservices platform: React on the frontend, NestJS on the backend, Prisma over PostgreSQL and Redis for the queues, deployed on AWS. The app talks to the city's existing management and authentication systems — and to payment platforms like Mercado Pago and Plus Pagos — without breaking anything.

mailing inside the main backend

Discarded path

Discarded path: mailing lived coupled to the main backend. I migrated it to a separate service that concentrates all notifications and messaging — the core deploys without putting emails at risk, and each piece scales on its own.

the consultancy

A project built at Crombie, the consultancy where I work, for the Santa Fe Municipality. Public software with private-consultancy standards: documentation, clear communication and deliveries that don't fall over.

QUEUE SYSTEM

retries · notifications · events

My strong suit on this project: I designed the retry and event-queueing system. Notifications and messaging decoupled from the request with Redis queues — absorb spikes, retry failures and never lose a single message.

notify thousands → queues, not loops

The decision behind the queues: sending thousands of notifications inside the request is how you take the service down. A queue makes it async, auditable and retryable.

CITY PAPERWORK NOW STARTS ON YOUR PHONE

appointments, fines & payments in one app

In production for the citizens of Santa Fe: the appointment core I built, integrated payments, and the direct messaging between citizens and municipal agents — which I also implemented end to end.

STACK

TypeScript at both ends: React up front, NestJS behind, Redis for messaging, notification and event queues, Prisma over PostgreSQL and deployment on AWS. Deliberately boring architecture: in government software, what doesn't fail wins.