Live data from Hacker News

HTTP/1 should die; HTTP/2 can do everything HTTP/1 could, only faster

medium.com

61–62 of 62 posts

Re: HTTP/1 should die; HTTP/2 can do everything HTTP/1 could, only faster

#61
post #59
post #57

Earlier quoted context omitted.

I’ve looked at quart and it looks interesting but is there much point to running an async webserver for APIs mainly reliant on db-access if we use SQLAlchemy for database connections? I’m under the impression that since the db stuff still is sync/blocking we won’t win much by running an asgi server instead of WSGI.

Give peewee-async as shot if you'd like async DB access as well. https://peewee-async.readthedocs.io/en/latest/ Looks like Gino is a new project trying to bake asyncio ORM on top of sqlalchemy core: https://github.com/fantix/gino

While interesting for greenfield development and experiments I'd say that it's most often a to big of a leap to change both ORM (with all db-access-code) and microframework at the same time for a well established project at 20KLOC+.

Re: HTTP/1 should die; HTTP/2 can do everything HTTP/1 could, only faster

#62
post #61
post #59

Earlier quoted context omitted.

Give peewee-async as shot if you'd like async DB access as well. https://peewee-async.readthedocs.io/en/latest/ Looks like Gino is a new project trying to bake asyncio ORM on top of sqlalchemy core: https://github.com/fantix/gino

While interesting for greenfield development and experiments I'd say that it's most often a to big of a leap to change both ORM (with all db-access-code) and microframework at the same time for a well established project at 20KLOC+.

For sure, definitely not a good path for an existing app :) You can use the sqlalchemy-core via async via a few projects (https://github.com/RazerM/sqlalchemy_aio) but for the full ORM there's no option, as far as I know.
Post reply on HN