# Help designing fire and forget server for large batch inference

**URL:** <https://discuss.ray.io/t/help-designing-fire-and-forget-server-for-large-batch-inference/12953>\
**Category:** Ray Serve\
**Created:** [November 27, 2023, 2:25pm UTC](https://discuss.ray.io/t/help-designing-fire-and-forget-server-for-large-batch-inference/12953 "2023-11-27T14:25:10Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![jonaz](https://avatars.discourse-cdn.com/v4/letter/j/e95f7d/32.png) [@jonaz](https://discuss.ray.io/u/jonaz)\
**Post date:** [November 28, 2023, 10:23am UTC](https://discuss.ray.io/t/help-designing-fire-and-forget-server-for-large-batch-inference/12953/2 "2023-11-28T10:23:29Z")

</div>

Well, after posting this here I did some digging and found this thread [Job Queue in Ray? - #24 by ericl](https://discuss.ray.io/t/job-queue-in-ray/1139/24)

Which led me to these RFCs

- [[RFC] Job queueing functionality with Ray Serve + Workflows · Issue #21161 · ray-project/ray · GitHub](https://github.com/ray-project/ray/issues/21161)
- [[RFC] Async request support in Ray Serve · Issue #32292 · ray-project/ray · GitHub](https://github.com/ray-project/ray/issues/32292)

And to discovering the existence of [Ray Workflows](https://docs.ray.io/en/latest/workflows/index.html), which could cover my use cases I believe 🙂

But anyway, I’d appreciate guidelines on how to use Workflows to design something like that, if anybody has some tips or best practices. I also know it’s still in Alpha.

Excited to see the development of the Async requests on Serve as well!  
What I’d suggest is to make Ray Workflows more visible, it took me quite a while to find out this existed, and I think use cases like mine are becoming more and more common (as the second RFC suggests) 🙂

---

_[View the full topic](https://discuss.ray.io/t/help-designing-fire-and-forget-server-for-large-batch-inference/12953)._