Mohammad-Amine BANAEI - Go & Node.js Architect
I don't just deliver code
I deliver outcomes and capability. You get a senior engineer who builds scalable, resilient systems that solve your immediate business problems, following a proven, full-lifecycle process.
Simultaneously, you get a collaborator who integrates with your team, shares knowledge, and leaves your organization more skilled and self-sufficient.
This combination ensures not only a successful project but also a stronger, more capable team for the future.
Cut cloud costs, reduce latency, and eliminate deployment anxiety.
Architecting systems that handle thousands of concurrent connections without crashing.
Moving from manual 'ClickOps' to automated GitOps. Turn risky Friday deployments into boring non-events.
Eliminating knowledge silos. I train your engineers to master Go and Cloud-Native tools, preventing vendor lock-in.
The "Black Box" Panic (Observability)
The Pain: "Our system is down, customers are complaining, and we have no idea why. It takes us 4 hours to find the root cause."
The Fix: Precision Instrumentation.
I don't settle for generic logs. I build custom monitoring instrumentation that creates explicit visibility into network transport layers.
The Proof: Developed a custom HTTP monitoring service in Go that captures latency and error metrics at the transport level, reducing diagnostic time from hours to minutes . This moves your team from "Guessing" to "Fixing."
The "Data Stagnation" Fix
The Pain: "Our analytics are useless because the data is hours old."
The Architecture: Parallelized Query Execution & MongoDB Aggregation
The Impact:
- 7x Velocity Increase: Reduced CSV export time from 15 minutes to <2 minutes for 100k+ records
- Efficiency: Eliminated blocking processes, allowing marketing teams instant access to data
The "Latency" Fix
The Pain: "The app crashes or lags when user traffic spikes."
The Architecture: Real-time Redis ecosystem + High-Performance Webhooks
The Impact:
- <100ms Latency: Maintained sub-100ms response times for thousands of concurrent participants during live contests
- Scale: Zero message loss during "thundering herd" events via optimized Node.js/Go logic
From Kernel to User Interface
Infrastructure Level: Deep experience building Kubernetes clusters from scratch, including NFS provisioning, Ingress routing (Traefik), and custom operators for monitoring deployments.
Application Level: Expertise in Go concurrency patterns and Clean Architecture, moving beyond MVPs to build full-featured backends with gRPC and REST adapters.
Workflow Level: Implementation of end-to-end CI/CD pipelines (GitHub Actions/GitlabCI + ArgoCD) that reduce release times from hours to minutes, with the full security suite (test + scan).
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…
Why migrate to Go if our team knows Node.js?
Node.js is excellent for prototyping, but Go provides the raw concurrency and stability needed for scale. I implement 'Strangler Fig' migrations so you can upgrade critical services without disrupting your existing team.
Do you only write code?
No. I am a 'Full-Cycle' engineer. I handle the architecture, the Go implementation, and the Kubernetes automation to ensure it runs reliably in production.