admin VS fastapi-crudrouter

I know about https://www.jhipster.tech/ and https://github.com/api-platform/admin but they are all a little bit different.

I think the idea is that FastAPI does one thing and does it well. You can mix in other parts of what you need, in the same way FastAPI itself leans on great projects.

SQLAlchemy + Alembic are standard because they're robust and well-know, but there are alternatives (particularly with async)[0][1]

For admin you can FE it with something like react-admin which has pluggable data providers, or api-admin[3]

[0] https://github.com/tortoise/tortoise-orm

[1] https://ponyorm.org/

[2] https://github.com/api-platform/admin

FastAPI does have an equivalent. Something like this? https://github.com/awtkns/fastapi-crudrouter

I can't show any pics cuz of uk NDA and all that. I can tell you the gist of it though. FastAPI is already pretty good at the abstraction part. Our middleware had a lot of rerouting and it was basically just a bunch of redundant functions. I just used this cool ass package https://fastapi-crudrouter.awtkns.com/ and used the partial function from functools to generate endpoints for every scenario/db tables.

Thanks, that's a really helpful example.

Where I think this could be taken to the next level of reusability is in modularising the front-end into API-specific components. For example, the login behaviour could depend on FastAPI-Users, with a sibling frontend library containing components that implement the same login flow. Adding user behaviour is then a matter of using the same third-party library on the front and back end.

This approach could be extended to other components such as an admin panel (perhaps using https://github.com/awtkns/fastapi-crudrouter), or a blogging component.