Rename `router.py` to `routes.py` for better clarity

[degisew]

Hi,

I’ve been exploring your project structure and really appreciate how you’ve applied Domain-Driven Design (DDD) principles — it's well-organized! However, I wanted to suggest a small change regarding the naming of the router.py file.

Since we typically define multiple routes, I think routes.py would be a more descriptive and clearer name. It's similar to how we use urls.py in Django, which helps in maintaining clarity across the project.

What are your thoughts on this?

Thanks!

[xshapira]

@degisew To me this also made sense in the past. But when you look at the FastAPI official documentation, the variable is always router, not routes. This aligns the filename with what it contains - a single APIRouter instance that groups related endpoints. In Django, urls.py contains URL patterns and mappings; in FastAPI, router.py contains an actual router object that handles routing logic. Fundamentally different things.

Even though each router file defines multiple routes, you can think of it this way: we're not storing routes, we're storing a router that happens to define routes. We name it after what it is (a router object), not what it contains (multiple routes).