FastAPI Without Spaghetti in Routing
In WikiMind, we split routes and business logic: view.py now contains only routing, while all logic lives in controller.py. That made testing, CI, and refactoring simpler.
At WikiMind, we eventually ran into the classic backend problem: FastAPI routes started filling up with logic, and maintaining them felt like digging through an old box of cables 😅 So we set a hard rule: view.py is for routes only, and all business logic goes into controller.py.
What did that give us? Testability without an HTTP context. We run controllers with regular unit tests, without starting a server, without pain. For the team, this is a must-have: faster CI, easier refactoring, less magic in endpoints.
The best part is that the pattern held up at scale. We rolled it out across all 48 business modules of the backend, and the architecture did not turn into a pumpkin. Against the backdrop of the AI-first product trend and faster release cycles, that matters even more: when features move quickly, the code still needs to stay readable, not end up as “if it works, don’t touch it.”