<story><title>Stateless – Evolving the architecture of Elasticsearch to simplify deployment</title><url>https://www.elastic.co/blog/stateless-your-new-state-of-find-with-elasticsearch</url></story><parent_chain></parent_chain><comment><author>ianbutler</author><text>Many of the people commenting don&amp;#x27;t realize that for the majority of ES users, it is a pain in the butt to manage and scale their cluster storage in lock step with their compute. Most companies use ES for relatively small scale search with people who are not experts in managing an ES cluster, or really infra at all.&lt;p&gt;A cloud offering that decouples storage from compute makes this a lot easier and becomes more of a no brainer for 90% of the use cases.&lt;p&gt;If you&amp;#x27;re an outlier with TBs or PBs of search data this probably you can keep using on prem if you want. Though I don&amp;#x27;t really immediately grant that it&amp;#x27;s worse for your usecase, especially when object storage is insanely cheap and supposing they provide a compat layer for S3 you can get away with everything from R2, S3, Ceph, Minio, Backblaze, etc. This is very much a case you should benchmark&amp;#x2F;analyze as a proper engineer.&lt;p&gt;I&amp;#x27;ve managed many TB ES clusters. This would have reduced my cost and time to manage it so I could focus on other features that would have benefitted my users.</text></comment>
<story><title>Stateless – Evolving the architecture of Elasticsearch to simplify deployment</title><url>https://www.elastic.co/blog/stateless-your-new-state-of-find-with-elasticsearch</url></story><parent_chain></parent_chain><comment><author>apendleton</author><text>Quickwit is another project aiming at this sort of stateless search: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;quickwit.io&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;quickwit.io&amp;#x2F;&lt;/a&gt; . I&amp;#x27;ve been keeping an eye on it for a possible project that would involve wanting to offer search over a lot of data for an application that wouldn&amp;#x27;t have very many users, such that keeping a big ES box around all the time would be needlessly expensive; I had been looking for a search situation where my only always-on costs were for storage, and I could pay for compute as needed (and ideally also separate paying for indexing compute, which doesn&amp;#x27;t happen often in this application, from search compute).&lt;p&gt;Interesting that ES might also end up with this kind of an offering.</text></comment>