You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have built a service using FastAPI and FastStream. Given that the peak QPS of requests exceeds the service's processing capacity, I need a queue to cache messages so that consumers can retrieve and process them sequentially.
Could you please review my code and assess whether the designed structure is reasonable? I've noticed that while publishing is fast, it takes a long time for the client to receive synchronous responses.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have built a service using FastAPI and FastStream. Given that the peak QPS of requests exceeds the service's processing capacity, I need a queue to cache messages so that consumers can retrieve and process them sequentially.
Could you please review my code and assess whether the designed structure is reasonable? I've noticed that while publishing is fast, it takes a long time for the client to receive synchronous responses.
Beta Was this translation helpful? Give feedback.
All reactions