asymmetric VS fastapi-crudrouter

APIs are the way to expose your creations to the web. But it can be a bit frightening to learn how to create APIs from scratch, and sometimes it may even require you to re-write your code to match a certain framework. That's why I built Asymmetric! With Asymmetric, you can add 1 line to any function you have already written and immediately transform it into an API. Let's see an example! Imagine that you have the following method on your beautiful machine learning python file named predictor.py:

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.