Is it really advisable to try to run fastapi with predominantly sync routes in a real world application?

• starlette

  55 9,491 9.2 Python

  The little ASGI framework that shines. 🌟

  

In this thread, starlette people admitting they don’t have anywhere near the tuning features necessary for more heavily sync oriented people https://github.com/encode/starlette/issues/1724

• fastapi

  465 70,779 9.8 Python

  FastAPI framework, high performance, easy to learn, fast to code, ready for production

Lack of docs explaining how to deal with configuring timeouts which is absolutely essential when using sync workers, and for example this absolute trainwreck of a discussion about configuring timeouts, which the lead dev / creator of fastapi fails to contribute to or offer any guidance https://github.com/tiangolo/fastapi/discussions/7364

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• asgiref

  17 1,391 7.5 Python

  ASGI specification and utilities

  

• dispatch

  20 4,594 9.9 Python

  All of the ad-hoc things you're doing to manage incidents today, done for you, and much more!

  

• mangum

  17 1,594 2.5 Python

  AWS Lambda support for ASGI applications

In the real world I'm never using static cloud resources. It's all serverless, containers, or horizontal auto-scaling. I let the infrastructure handle asynchronous scaling when needed. For FastAPI specifically I've used Mangum: https://mangum.io/ to provide the asynchronous invocation below the ASGI layer. Then all my FastAPI code can just be synchronous.

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

Suggest a related project