I Built My Own API Gateway in Rust — Here's What I Learned

Every backend project I've worked on eventually hits the same wall.

You start clean — one service, simple routes, everything works. Then slowly the requirements creep in. "We need rate limiting." "Can we add auth middleware?" "What happens when the user service goes down — does it take everything else with it?"

You either bolt these things onto every service individually, copy-paste the same middleware across projects, or pay for a managed gateway like Kong or AWS API Gateway and hope it does what you need.

I wanted to actually understand how these things work under the hood. So I'm building one — and this is what I've learned so far.

What is Ferrox?