shillelagh VS fastapi-crudrouter

It should be possible (have not tried myself):

https://preset.io/blog/accessing-apis-with-superset/

"Shillelagh (ʃɪˈleɪlɪ) is a Python library and CLI that allows you to query many resources (APIs, files, in memory objects) using SQL. It's both user and developer friendly, making it trivial to access resources and easy to add support for new ones"

https://github.com/betodealmeida/shillelagh

Shillelagh (https://github.com/betodealmeida/shillelagh) is a wrapper that allows users to query APIs using SQL. You can join weather data with a Google spreadsheet, for example. It always need more help in adding adapters for new data sources.

You can read more about it in the architecture document.

I'm adding this to Apache Superset today!

- Shillelagh (https://github.com/betodealmeida/shillelagh): query API's .. using SQL!

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.