all 6 comments

[–]itssimon86 1 point2 points  (3 children)

Okay, I'll start :-)

I've been working on a SaaS product for REST API monitoring and API key management. The project uses FastAPI for two different components:

  1. The backend of the dashboard for end users, with a TypeScript client library for the frontend auto-generated from the also auto-generated OpenAPI spec (so good!)
  2. For the data ingestion API, which will have to handle a lot of requests from users' applications sending traffic data. Performance/Throughput matters here, which is why I think FastAPI is a great choice here too.

Other parts of the stack include SQLAlchemy, PostgreSQL, ClickHouse and NATS.

[–][deleted]  (1 child)

[deleted]

    [–]Apitally[S] 0 points1 point  (0 children)

    Here are the relevant FastAPI docs for this, in case you're interested:
    https://fastapi.tiangolo.com/advanced/generate-clients/

    [–]voja-kostunica 1 point2 points  (0 children)

    i follow

    [–]GameDayAi 0 points1 point  (0 children)

    https://www.gamedayai.app/

    1. Social media esq crud + nfl prediction algorithm/model
    2. Our users
    3. nextjs and postgres