Hi HN, Quickwit cofounder here!<p>Quickwit is a cloud-native search engine for observability, and we have just released a significant upgrade with performance improvements, extended Elasticsearch API compatibility, and better integration with OpenTelemetry tools, Grafana, and Jaeger.<p>This release is also a significant milestone as we have been witnessing users of the nightly version of Quickwit deploy clusters with hundreds of nodes, ingest hundreds of terabytes of data daily, and enjoy additional cost savings. We are very excited to put it in the hands of all of our users.<p>One report particularly compelling is coming from a company ingesting hundreds of terabytes of logs daily and migrating from Elasticsearch to Quickwit, dividing their compute costs by 5x and storage costs by 2x while increasing retention from 3 to 30 days. They also increased durability, accuracy with exactly-once semantics coming from native Kafka support, and elasticity; you can read more about their performance achievements in our release blog post [0].<p>This gives us great confidence in our ability to deliver a robust OSS alternative to Elasticsearch, Datadog, or Splunk and we are eager to get feedback and suggestions. To give you a glance at our roadmap, here are the next key features:<p>- Quickwit on AWS Lambda (Q1)<p>- Native distributed ingest (Q1)<p>- Pipe-based query language (Q3-Q4)<p>- Metrics support (Q3-Q4)<p>[0] Release blog post: <a href="https://quickwit.io/blog/quickwit-0.7" rel="nofollow">https://quickwit.io/blog/quickwit-0.7</a><p>[1] Open Source Repo: <a href="https://github.com/quickwit-oss/quickwit">https://github.com/quickwit-oss/quickwit</a><p>[2] Home Page: <a href="https://quickwit.io" rel="nofollow">https://quickwit.io</a>
WOW this is a big release! I want to learn more about the EBS to S3 move. What are some of the constraints and how are you managing the latency with S3?