Best Practices for Building APIs in Laravel and Go: Notes from a Real Project

Thu, 07 May 2026 10:28:00 +0700

In the PHP-to-Go migration project I worked on, there was a phase where I had to audit every existing route and controller. The goal was simple: before migrating, understand which patterns are solid and which need to go. The result? Well, it was… enlightening hahaha.

The project profile looked like this:

460+ routes in api.php¹
58 controllers of various sizes and patterns
5 auth guards: user-api, partner-api, open-api, open-api-limited, tms-api
Varied rate limiting: from 3/minute up to 100/minute

This article isn’t a “how to build an API” tutorial. These are notes on patterns and anti-patterns I found, plus how the same patterns map to Go. So if you’re migrating or starting a new project, hopefully you can skip some of the mistakes I already discovered hehe~

Api on Blogfolio Najib

Best Practices for Building APIs in Laravel and Go: Notes from a Real Project