5 ms·

Thank you for sharing. I use mainly flask and restful flask. However restful flask has been deprecated, so I was really interested in FastAPI. Then someone poi

Thank you for sharing. I use mainly flask and restful flask. However restful flask has been deprecated, so I was really interested in FastAPI. Then someone pointed out the number of open issues on the FastAPI project, so I got spooked. Flask maybe has quite a few frameworks for implementing rest API. Not sure what the future holds for Flask. As you pointed out > A backend comes with all sorts of baggage: databases, managing user data, authentication, backups, and increased server load. With Flask being a microframework and barebones, going through this list becomes a chore unless you have built dozens of webapp and have some kind of template. So I kinda gave up on web-backend entirely and moved towards firebase. Most of the complicated stuff will happen on the VPS side of things and will be communicated to firebase via the SDK.

wcedmisten 4y ago
Yeah that sounds like a good choice for managing complexity. Probably a trade-off with cost I'm guessing. For my project I was trying to get the cost as low as possible, since it's just a side project for me. Interesting point about the open issues, I didn't notice that, but does seem like it could be an issue for the longevity of the project.
foolswisdom 4y ago
I always liked fastapi and didn't have any problems, so your comment on issues made me check. Currently there are 16 open issues. However, I believe (based on vague memories) that there used to be a ton of issues on the fastapi repo that were basically support requests. Going throw some closed issues, it seems that these were closed and/or converted to discussions.