Re:Show HN: HTTP/2 Python-Asyncio Web Microframework
by pgjones on Monday April 23, 2018 @03:09PM
(#16906441)
Have you any experience with GINO (https://github.com/fantix/gino) or Peewee-Async (https://github.com/05bit/peewee-async)? These look to be feasible alternatives.
Re:Show HN: HTTP/2 Python-Asyncio Web Microframework
by fantix on Saturday April 28, 2018 @12:33AM
(#16946075)
Working on a Quart extension for GINO now.
Re:Show HN: HTTP/2 Python-Asyncio Web Microframework
by theptip on Monday April 23, 2018 @03:43PM
(#16906729)
An interesting deep dive on why this is the case (from 2015), in case anyone wants to know more:
http://techspot.zzzeek.org/2015/02/15/asynchronous-python-an...
Re:Show HN: HTTP/2 Python-Asyncio Web Microframework
by tomchristie on Monday April 23, 2018 @04:38PM
(#16907174)
One thing I've never been able to reconcile is Mike Bayer's article there, set against Yury Selivanov's reported results for `asyncpg`, which at least as they're presented do indicate a significant difference in throughput.
https://github.com/MagicStack/asyncpg
They're both incredibly experienced developers, and I don't have any good steer on the discrepancy.
Would love to see some independent benchmarking on a typical use case to get a clearer picture on how valuable (or not) asyncio is for high-throughput database operations.
SA unfortunately, does not have a asynchronous version (its quite complex as it is). Therefore, I think it would require quite a lot of work, in order to actually get a standard flask app to work with quart.
However, if you've built your data access layer directly on psycopg, then I think you're good to go.