FastAPI starter setup question

[asynckeel-max]

Hi! I found your FastAPI backend template while exploring different starter architectures.

I'm currently researching how developers structure FastAPI backends since I'm building a lightweight SaaS backend starter called AsyncKeel.

In your experience, what part of starting a new backend project tends to slow developers down the most?

[Dimakoua]

Hey there! Thanks for reaching out. From my experience, the major roadblock isn’t necessarily in crafting code; it’s Architectural Decision Fatigue.

More concretely, developers get stuck in these three areas:

Folder Structure & Boundaries: If boundaries aren't clearly defined from day one, business logic inevitably leaks into your controllers. This traps your code, making it incredibly hard to reuse for background workers or CLI tools later on. In a solid setup, a developer shouldn't have to waste time guessing which folder a file belongs in, or figuring out how to slice a new feature across different layers. That’s exactly what this template aims to solve providing a clear, out-of-the-box structure with distinct layers and naming guidelines so you can stop overthinking the architecture and just build

Middleware & Permissions: Most devs want the 'plumbing' solved from day one. Implementing secure routing with JWTs and role-based access requires a clean middleware setup. If adding a new middleware is complicated, the whole project slows down

Test Isolation: Creating a testing environment where an async database is nicely managed and/or rolled back using pytest fixtures. If it’s a pain to set up initially, devs will likely just skip it and not write tests at all.