Your Node.js App is Drowning. Let's Fix That.
Your MVP got you here. It won't get you further.
I migrate performance bottlenecks to high-concurrency Go and automate your infrastructure—so deployments become boring and your platform keeps pace with revenue.
We turn "It works on my machine" into "It scales in production"
The Pillars of a Scalable System
Eliminate Latency
I stop the backend performance degradation that kills user retention and erodes trust. You get high-throughput systems that deliver sub-200ms response times.
Operational Stability
I turn risky, manual deployments into boring, routine events. You get a self-healing infrastructure with zero-downtime releases via GitOps and Kubernetes.
Build Self-Sufficiency
I don't create dependencies; I eliminate them. I enable your team to own the system I build, transferring knowledge so you're not reliant on a single expert.
How I Deliver Results: My Core Engagements
The Performance Migration
For Who ?
For leadership whose core Node.js or PHP service can no longer keep up with user demand.
Deliverables
- A surgical rewrite of critical performance "hot paths" into high-concurrency Go.
- Implementation of a clean, maintainable architecture for long-term velocity.
- Measurably lower cloud costs via reduced CPU/RAM usage.
The Infrastructure Modernization
For Who ?
For startups ready to graduate from risky manual deployments to professional-grade operations.
Deliverables
- A secure Kubernetes foundation with a GitOps workflow (ArgoCD) for automated, zero-downtime releases.
- A complete observability stack (Prometheus, etc.) to diagnose production issues in minutes, not hours.
- A repeatable, confident process for shipping features.
The Internal Platform
For Who ?
For teams whose developer velocity is being throttled by repetitive tasks and workflow friction.
Deliverables
- Custom command-line tools (CLIs) in Go to automate frequent developer workflows.
- Automated logic flows connecting disparate internal systems and APIs.
- More time for your engineers to focus on building your core product.
From Theory to Production: Proven Impact
Processed 1M+ Rows in Under 3 Minutes
The Challenge
Critical business data was bottlenecked by slow ingestion pipelines and manual entry, with legacy exports taking 15+ minutes to process.
The Solution
Architected a high-concurrency ingestion pipeline using Go, AWS Lambda, and ECS Fargate. Implemented parallel query logic and MongoDB aggregations to maximize throughput.
The Result
Achieved a steady processing rate of 1,000,000+ CSV rows in <3 minutes and reduced report generation time from 15 minutes to <2 minutes, ensuring zero duplicate processing.
Tech Stack
Go, AWS Lambda, ECS Fargate, MongoDB Aggregations
92% Reduction in Deployment Overhead
The Challenge
A manual, "wild west" release process resulted in a 40% failure rate and multi-hour deployment windows, paralyzing the engineering team.
The Solution
Implemented a strict GitOps workflow using ArgoCD on Kubernetes, enforcing declarative infrastructure management.
The Result
Slashed deployment time from 2 hours to under 10 minutes and collapsed the failure rate to <5%, creating a "zero-touch" release environment.
Tech Stack
Kubernetes, ArgoCD, Helm, Kustomize
Sovereign Cloud Architecture from Bare Metal
The Challenge
Demonstrating the ability to build production-grade infrastructure without relying on managed cloud providers (AWS/GCP) to hide complexity.
The Solution
Built and operated a highly available (HA) 3-node Kubernetes cluster from the hardware up, including custom networking (MetalLB), storage (NFS), and secrets management (Infisical).
The Result
Automated total cluster recovery (Disaster Recovery) from 3+ hours to <20 minutes via Ansible/Kubespray, proving mastery of the entire infrastructure stack.
Tech Stack
Ansible, Kubespray, HA Kubernetes, MetalLB, Cilium CNI
Who I Am
I am a Production-Ready Backend Architect who bridges the gap between application logic (Go/Node.js) and infrastructure (Kubernetes).
My Philosophy
Software doesn't stop at git push. I build systems that are observable, resilient, and easy to operate.
The Difference
While others rely on managed cloud services to hide complexity, I have the expertise to build and manage bare-metal Kubernetes clusters from scratch. I know exactly how the engine works.
No Black Boxes
I refuse to build systems only I can understand. I document as I build, ensuring zero vendor lock-in on my services.
Proven Educator
At PerfectStay: I trained Java and Frontend teams to become autonomous on Go microservices, conducting targeted troubleshooting sessions.
At ESGI: I designed the Master’s curriculum and trained 200+ engineers on Kubernetes architecture, CI/CD pipelines, and Microservices design.
Your Benefit
When our contract ends, your team will be fully upskilled and ready to take the helm.
Contact
Transparency by Default
No "big bang" deliveries. You see progress every week
Introduction
We left off on a high note. The Kubernetes cluster was alive. But as any engineer knows, a working system is often just the prelude to the next, more interesting problem. While the cluster was technically functional, its architecture had a hidden Achilles' heel: a single point of failure for all incoming traffic.
My mission was clear: eliminate it. The tool for the job was MetalLB, and the task seemed simple. I was wrong.…
You’re in the final interview for a Senior Platform Engineer role. You’re at the whiteboard. The CTO leans forward and asks, "How would you design our observability strategy from scratch?"
You know the tools. You've done this before. Confidently, you dive straight in : "I'd use Prometheus for metrics, Loki for logs because it's cost-effective, OpenTelemetry for tracing...".
The CTO cuts you off. "I don't need a list of tools. I asked for a strategy."
At this moment, you realise that something is missin…
Introduction
For as long as I can remember, I’ve been fascinated by systems—how they work, how they break, and how they can be made better. As a developer, I’ve always sought ways to streamline my workflows and take control of my tools. That’s why I decided to build my own Kubernetes cluster at home. Driven by my passion for systems and coding, I wanted to create a self-owned cloud. I also believe that individual control of digital infrastructures leads to a more balanced world. Setting up eve…
Frequently Asked Questions
Clear answers to your technical and operational questions
My entire team is built around Node.js/Python/PHP. Introducing Go seems like a huge risk.
It is not a rewrite; it is a surgical optimization. Node is excellent for I/O, but struggles with heavy concurrency. I introduce Go strictly for the 'hot paths'—the 20% of services consuming 80% of your resources—while keeping your existing ecosystem intact.
So, are you a DevOps engineer or a Backend developer?
I am a Production-Ready Backend Architect. Most backend devs don't know how to deploy, and most DevOps engineers don't understand business logic. I do both: I write the code (Go) and I configure the GitOps pipeline (ArgoCD/Kubernetes) to ensure it runs reliably in the wild.
What happens when the mission ends? Will we be left with a black box?
Never. I am a certified technical trainer. Part of my deliverable is the 'Handover Protocol': I write the runbooks and conduct live workshops to train your team, ensuring they are fully autonomous before I leave.