# Roadmap for "Stateless" Elasticsearch

**URL:** https://discuss.elastic.co/t/roadmap-for-stateless-elasticsearch/316107
**Category:** Elasticsearch
**Created:** [October 7, 2022, 7:41pm UTC](https://discuss.elastic.co/t/roadmap-for-stateless-elasticsearch/316107 "2022-10-07T19:41:55Z")
**Posts on this page:** 10
**Page:** 1

<div class="post-metadata">

### Author: ![benjismith](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benjismith/32/106309_2.png) [@benjismith](https://discuss.elastic.co/u/benjismith)
#### Post date: [October 7, 2022, 7:41pm UTC](https://discuss.elastic.co/t/roadmap-for-stateless-elasticsearch/316107/1 "2022-10-07T19:41:55Z")

</div>

I read yesterday's blog post about the future of a "stateless" Elasticsearch architecture, where one of the big benefits is the ability to scale indexing workloads separately from search workloads...

> **[Stateless — your new state of find with Elasticsearch](https://www.elastic.co/blog/stateless-your-new-state-of-find-with-elasticsearch)**
>
> Discover this future of stateless Elasticsearch. Learn how we’re investing in building a new fully cloud native architecture to push the boundaries of scale and speed.

I have a 30+ node Elastic cluster that ingests (and deletes) 6 billion records every day, and it’s been a constant struggle to keep the indexing workload from interfering with search performance. So the new architecture sounds like EXACTLY what we need.

Do you have a rough idea of the release timeline?

---

<div class="post-metadata">

### Author: ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [October 7, 2022, 9:39pm UTC](https://discuss.elastic.co/t/roadmap-for-stateless-elasticsearch/316107/2 "2022-10-07T21:39:37Z")

</div>

While we appreciate there is a tonne of excitement around this topic, we don't publish release timelines sorry to say 🙂

---

<div class="post-metadata">

### Author: ![benjismith](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benjismith/32/106309_2.png) [@benjismith](https://discuss.elastic.co/u/benjismith)
#### Post date: [October 8, 2022, 1:24am UTC](https://discuss.elastic.co/t/roadmap-for-stateless-elasticsearch/316107/3 "2022-10-08T01:24:32Z")

</div>

Okay... How about a slightly different question.

Is this the pre-launch announcement of Elasticsearch 9?

😉

---

<div class="post-metadata">

### Author: ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [October 8, 2022, 1:31am UTC](https://discuss.elastic.co/t/roadmap-for-stateless-elasticsearch/316107/4 "2022-10-08T01:31:30Z")

</div>

I haven't heard anything, so I would say no.

---

<div class="post-metadata">

### Author: ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [October 8, 2022, 7:51am UTC](https://discuss.elastic.co/t/roadmap-for-stateless-elasticsearch/316107/5 "2022-10-08T07:51:13Z")

</div>

The way I read the blog post, this may be a dedicated future Elastic Cloud feature as that is mentioned in several places.

---

<div class="post-metadata">

### Author: ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)
#### Post date: [October 8, 2022, 2:54pm UTC](https://discuss.elastic.co/t/roadmap-for-stateless-elasticsearch/316107/6 "2022-10-08T14:54:17Z")

</div>

I read it the same way, it looks like it will be a Elastic Cloud only feature.

Since it will rely in a search model similar to searchable snapshots, if it lands in the self-managed version it will probably be on the Enterprise license.

Or maybe this could be seen as a hint that Elastic will focus on the cloud offering and the self-managed version will lack some features in the future.

---

<div class="post-metadata">

### Author: ![BenB196](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benb196/32/83401_2.png) [@BenB196](https://discuss.elastic.co/u/BenB196)
#### Post date: [October 9, 2022, 1:26pm UTC](https://discuss.elastic.co/t/roadmap-for-stateless-elasticsearch/316107/7 "2022-10-09T13:26:13Z")

</div>

I think this idea is kind of interesting, from a high-level architecture overview, it seems very similar to: [thanos](https://github.com/thanos-io/thanos), which has shown the feasibility of this type of architecture (even as user deployable).

One thing I'd be curious about, are the intended use cases for this new architecture. The blog post doesn't really state the exact use-cases this setup is intended for but seems to imply that its mainly for logs/metrics/append-only style use-cases.

I'd also be interested in seeing the searching side benchmarks. While the indexing improvements are pretty significant, it would be interesting to know if there are any trade-offs for the searching side.

---

<div class="post-metadata">

### Author: ![Dustin\_Tennill](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dustin_tennill/32/79039_2.png) [@Dustin\_Tennill](https://discuss.elastic.co/u/Dustin_Tennill)
#### Post date: [October 9, 2022, 4:41pm UTC](https://discuss.elastic.co/t/roadmap-for-stateless-elasticsearch/316107/8 "2022-10-09T16:41:54Z")

</div>

I'm curious about where this will leave on-prem customers. It's currently less expensive for my organization to run Elastic on servers we maintain. This could potentially change costs enough to make a difference for us.

Watching hopefully.

---

<div class="post-metadata">

### Author: ![Swissmountain](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/swissmountain/32/108071_2.png) [@Swissmountain](https://discuss.elastic.co/u/Swissmountain)
#### Post date: [October 10, 2022, 9:28am UTC](https://discuss.elastic.co/t/roadmap-for-stateless-elasticsearch/316107/9 "2022-10-10T09:28:46Z")

</div>

From me point of view, the high availability and data replication / horizontal scaling is a must-have no matter what the architecture is.  
I am curious to see how this would be adressed based on the simple architecture diagram here: [Stateless — your new state of find with Elasticsearch | Elastic Blog](https://www.elastic.co/fr/blog/stateless-your-new-state-of-find-with-elasticsearch)

If all these criteria are met and the respons time / speed is improved, this would be perfect.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [November 7, 2022, 9:29am UTC](https://discuss.elastic.co/t/roadmap-for-stateless-elasticsearch/316107/10 "2022-11-07T09:29:06Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
