Journey

The Goalixa Journey

The complete story of building Goalixa - from idea to production, through challenges and lessons learned.

This is the narrative story of how Goalixa evolved from a concept to a production-ready productivity platform. Each chapter represents a phase of the journey, with personal reflections and technical details.

Chapter 1: The Beginning

Why I Started Goalixa

The journey began with a simple problem: I needed a better way to manage my goals, projects, and daily tasks. Existing tools didn’t quite fit the way I think about productivity - I wanted something that could bridge the gap between high-level goals and daily action items.

Status: 📖 Story in progress Time Period: Initial concept and early development

Key Posts in this Chapter:

  • Coming soon: Full product introduction and vision

Lessons Learned:

  • Start with a clear problem statement
  • Build what you would use yourself
  • Keep the vision simple but ambitious

Chapter 2: Learning in Wartime

Building Under Crisis Conditions

Building a startup is hard. Building a startup during wartime in Iran with severe internet restrictions is exponentially harder. In March 2026, I found myself in exactly this situation - intermittent internet access, VPN services as the only connection method, and servers located outside the country.

Despite these challenges, I used the downtime to study deeply and plan the infrastructure upgrades that Goalixa would need.

Status: 🔄 Ongoing challenges Time Period: March 2026 - Present

Key Posts in this Chapter:

Lessons Learned:

  • Adaptability is everything when circumstances change
  • Use downtime productively - study and plan
  • Infrastructure resilience matters more than I thought
  • Remote access patterns become critical in crisis

Chapter 3: First Deployments & Early Architecture

From Monolith to Microservices

The early architecture of Goalixa was straightforward: three main services (app, auth, landing), each with its own subdomain and frontend. While this worked initially, it created problems:

  • Complex redirect flows between domains
  • Cookie and session consistency challenges
  • Fragmented UI ownership
  • High blast radius during incidents

The critical reliability issue became clear: when the app service went down, almost everything went down with it. This single-point-of-failure effect created unacceptable recovery pressure.

Status: ✅ Migration completed Time Period: February 2026

Key Posts in this Chapter:

Lessons Learned:

  • Microservices require unified frontend experience
  • API Gateway is essential for true microservices
  • Fragmented UIs slow down product iteration
  • Single points of failure create operational nightmares

Chapter 4: The PWA Transformation

Unifying the Frontend Experience

The biggest milestone in Goalixa’s early life was the successful migration to a Progressive Web App (PWA) architecture combined with an API Gateway. This transformed Goalixa from multiple fragmented UIs into a single, cohesive user experience.

The new flow became clear and simple:

PWA (app.goalixa.com) → API Gateway → Backend Services

Status: ✅ Completed and production-ready Time Period: February 20, 2026

Key Posts in this Chapter:

Lessons Learned:

  • One UI is better than many
  • BFF pattern keeps both frontend and backend clean
  • API Gateway enables true service independence
  • Migration is worth the effort

Chapter 5: Microservices Migration

Breaking Apart the Monolith

With the PWA and Gateway in place, the real microservices migration began. The target architecture included:

  • One unified frontend (PWA)
  • API Gateway as single entry point
  • BFF layer for client-focused aggregation
  • Domain services focused only on business logic
  • Clear service tiers (Level A: critical, Level B: non-critical)

Status: ✅ Foundation complete, migration ongoing Time Period: February 2026

Key Posts in this Chapter:

Lessons Learned:

  • Define service boundaries early
  • Not everything needs to be a service immediately
  • Tier-based criticality helps prioritize reliability work

Chapter 6: GitOps Journey with ArgoCD

Git as the Source of Truth

After setting up Harbor as the image registry, the next logical step was implementing GitOps with ArgoCD. The goals were clear:

  • Git as source of truth for deployments
  • Safer and more predictable releases
  • Better visibility of drift between desired and running state
  • Faster rollback and recovery during incidents

I implemented controlled sync initially, then moved toward automation for stable services.

Status: ✅ First phase complete Time Period: February 2026

Key Posts in this Chapter:

Lessons Learned:

  • Start with manual sync, then automate
  • Keep manifests versioned and reviewable
  • Monitor health immediately after sync
  • Git alignment enables fast rollbacks

Chapter 7: Challenges & Incidents

When Latency Became Real

The most significant learning moment came when latency moved from a dashboard metric to something I could feel directly while using the app. This happened after introducing the API Gateway and separating backend services from the frontend.

An incident on February 24-25, 2026, made this painfully clear. A PWA path/routing change caused noticeable slowness, visible in both monitoring graphs and real usage.

Status: 📚 Resolved, lessons documented Time Period: February 24-26, 2026

Key Posts in this Chapter:

Lessons Learned:

  • Performance is a product feature, not just an SRE metric
  • Every network hop must have clear value
  • Route changes are high-risk production changes
  • User-perceived latency is the real truth
  • Add observability before scaling complexity
  • Cache intentionally where safe and valuable

Chapter 8: Current State & Future Plans

Building for Production

As Goalixa approaches production readiness, the focus has shifted to reliability, staging environments, and sustainable development practices.

Current Priorities:

  • Implementing staging environment with Kustomize
  • Reducing deployment risk with proper dev → staging → prod flow
  • Improving observability with comprehensive monitoring
  • Using AI (Claude) effectively for faster development

Status: 🚧 In progress Time Period: March 2026 - Present

Key Posts in this Chapter:

Future Plans:

  • Complete staging environment implementation
  • Add Cilium for networking and security
  • Explore service mesh with Envoy
  • Implement event-driven architecture with NATS
  • Expand monitoring and alerting coverage

Journey Summary

Key Milestones 🎯

MilestoneDateStatus
Initial ConceptEarly 2026✅ Complete
Microservices DecisionFeb 2026✅ Complete
PWA + Gateway LaunchFeb 20, 2026✅ Complete
GitOps with ArgoCDFeb 2026✅ Phase 1 Complete
Latency IncidentFeb 25, 2026✅ Resolved
Staging EnvironmentMar 2026🚧 In Progress
Production LaunchTBD📋 Planned

Technology Choices

  • Frontend: Progressive Web App (PWA)
  • API Gateway: Nginx-based gateway
  • Backend: Python (Flask/FastAPI) microservices
  • Container Orchestration: Kubernetes
  • GitOps: ArgoCD + Harbor
  • Monitoring: Prometheus, Grafana, Alertmanager
  • Development: AI-assisted (Claude)

Personal Growth

Building Goalixa has been an incredible learning journey. From understanding microservices architecture to implementing GitOps, from handling production incidents to building during wartime - every challenge has taught valuable lessons about engineering, resilience, and product development.

The most important lesson: Great engineering is not just about writing code - it’s about building systems that stay fast, reliable, and understandable under real conditions.

Want the technical timeline? See the Timeline page for chronological post listings.

HomeAI & Automation