[QUESTION] Delivering real time JSON packages to clients on events

First check

• I used the GitHub search to find a similar issue and didn’t find it.
• I searched the FastAPI documentation, with the integrated search.
• I already searched in Google “How to X in FastAPI” and didn’t find any information.

Description

I have to deliver JSON packages to clients when specific events happens. I imagine building a FastAPI application where people can subscribe and add some callback. Is this the industry-standard of doing things (and is this the right place to look)? I imagine some /subscribe POST with callback instructions and /unsubscribe.

Alternatively I could require people to set up some kind of server to receive the data of course and then HTTP POST e.g.

If this question is out of scope here then please let me know and just close the question. Thank you.

[dbanty]

@mr-bjerre a common pattern (and then one I’ve followed in a few places) is to use the web sockets for very basic information only. Not sure how your schema is set up, but let’s say each new piece of news has some unique ID that users can use to pull from a normal FastAPI endpoint. You could, on publish, push just that new ID to clients via websocket. Then, the client could fetch the full details (with all the glory of the OpenAPI schema) with a normal HTTP call.

I’ve only used SocketIO, which utilizes websockets but also allows for long polling for older clients. It has some additional features that make sending/receiving events easy.

One other thing you might consider is using GraphQL instead of REST. GraphQL has a concept of subscriptions I believe (though I’ve never actually used them) and is supported fairly well on Starlette.

Either way I don’t think FastAPI itself will solve your real time problem

[NixBiks]

Ha sorry I don’t know why I thought he answered.

Thank you retnikt! 🙏