[ OK ]
rodmar@fedora: ~/battles/migracion-wordpress-lightsail-a-astro-cloudflare
rodmar@fedora:~/battles$ cat ./migracion-wordpress-lightsail-a-astro-cloudflare.md
---
title: "Operation: VELOCITY SHIFT"
role: "Lead Architect"
difficulty: 4/5
outcome: "Cost -80% | Latency -60%"
mission: "Strategic migration of this very personal blog from a legacy AWS Lightsail WordPress monolith to a high-performance modern architecture on Cloudflare."
---

📋 Mission Brief

Primary Objective: Eliminate technical debt and high operational costs of the previous version of rodmarzavala.com (hosted on AWS Lightsail), transforming it into the high-performance static site you are visiting right now.

Legacy State: The previous system operated on a heavy AWS Lightsail instance backed by a PostgreSQL database.

  • Cost: Disproportionately high for the traffic volume.
  • Maintenance: Constant manual cycle of updates, security patches, and resolving version conflicts.
  • Performance: Sluggish response times due to unnecessary dynamic server-side processing.
  • DX (Developer Experience): While the editor was familiar, the infrastructure management was a burden.

🛠️ Technological Arsenal

To execute this override, we deployed a precision-engineered artisanal stack:

  • Astro: The core engine for zero-JS-by-default performance and content-first architecture.
  • Cloudflare Pages: The global edge network ensuring instant delivery worldwide.
  • Wrangler (CLI): Command-line supremacy for local dev and edge deployment.
  • MDX: The perfect fusion of markdown content and component interactivity.
  • TypeScript: Type-safety layer ensuring code robustness.

⚔️ Battle Report

Phase 1: Extraction & Architecting

The relational model (PostgreSQL) was decommissioned in favor of a Content Collection architecture. We moved from dynamic database queries to build-time content generation, ensuring 100% uptime and zero database connection latency.

Phase 2: Feature Preservation

Critical capabilities were re-engineered for the static paradigm:

  • Search Protocol: Implemented via Pagefind for client-side static indexing.
  • Navigation: Handled natively by Astro’s file-based routing system.

🏆 Mission Outcome

The operation was a decisive victory.

  • Performance: Lighthouse scores hit a perfect 100/100.
  • Efficiency: Operational costs plummeted by migrating to the Edge.
  • Stability: Zero maintenance mode achieved—no more plugin nightmares.
  • Professionalism: The site now runs on a stack that reflects seniority and engineering excellence.

System Status: OPTIMAL Next Objective: Expanding the edge capabilities with Cloudflare Workers.

rodmar@fedora:~/battles$
cd ~
(Return Home)
[rodmar]
0:bash- 1:battles*
00:00:00
[ Press ESC or Click anywhere to close ]