I have some queries I am making that cause timeouts because the fetching and computing of the data takes too long on the server. I'm wondering what the best practice is for my specific stack in this case. And if there are any examples leveraging graphene for this.
My stack:
Potential options I am currently investigating:
- Polling the server until the data is ready.
- Use a subscription instead of a query. But based on these docs it alludes that perhaps polling is the preferred method.
In the majority of cases, your client should not use subscriptions to stay up to date with your backend. Instead, you should poll intermittently with queries, or re-execute queries on demand when a user performs a relevant action.
- Just increase the timeouts. I don't think this is great because the data I'm computing can change and become larger over time. Which would in turn require me to increase the timeout again.
与恶龙缠斗过久,自身亦成为恶龙；凝视深渊过久,深渊将回以凝视…
