opendal
quickwit
opendal | quickwit | |
---|---|---|
10 | 64 | |
2,858 | 6,175 | |
2.5% | 6.1% | |
9.9 | 9.8 | |
2 days ago | 1 day ago | |
Rust | Rust | |
Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
opendal
-
Welcome to Apache OpenDAL
Sounds likely.
The core part of OpenDAL is a Rust crate that provides fs-like APIs over different storage backends, but we also investigate providing other interfaces like a CLI. We have an experimental binary named `oli`[1].
You're welcome to start a discussion[2] to share how you use rclone and we may find it fit in OpenDAL's scope :D
[1] https://github.com/apache/incubator-opendal/tree/main/bin/ol...
-
Hey Rustaceans! Got a question? Ask here (49/2023)!
[profiles.mys3] type = "s3" region = "us-east-1" access_key_id = "foo" enable_virtual_host_style = "on" ``` The team at Opendal wrote a handcrafting config parser for the same use case, see. Since parsing configs in toml or json is a standard functionality, is there any recommended way?
-
Ask HN: Experience using your user's Google Drive instead of a database?
I've often felt we need an abstraction for just this. "Bring your own storage" so that you can sign up and provide a "bucket", then the service will write to that.
OpenDAL was on HN recently and would be a pretty decent abstraction to use for this: https://github.com/apache/incubator-opendal
-
Rust std:fs slower than Python
Totally unrelated but: this post talks about the bug being first discovered in OpenDAL [1], which seems to be an Apache (Incubator) project to add an abstraction layer for storage over several types of storage backend. What's the point/use case of such an abstraction? Anybody using it?
[1] https://opendal.apache.org/
-
S3 as the Storage Layer
https://github.com/apache/incubator-opendal
- Apache OpenDAL: A unified data access layer
- Apache OpenDAL
-
Way to Go: OpenDAL successfully entered Apache Incubator
A new big event in a few weeks, this may be the first project whose primary language is Rust to enter the Apache incubator. OpenDAL originated from the vision of creating a universal, unified and user-friendly data access layer. It came into being in late 2021, initially as a component of the Databend project.
-
[Need inspiration] Building the control plane of a search engine (Quickwit)
I was reading through the code of databend: https://databend.rs/ It's a "wrapper" over datafusion and does a lot of similar things to Quickwit. And yeah, to drive the index cluster they rely on https://github.com/datafuselabs/openraft && https://github.com/datafuselabs/opendal. I'd be interested about you thoughts on the project if you've already heard about it too.
-
[Announcement] Databend v0.7.0 Released!
Announce OpenDAL for object storage data access
quickwit
- Show HN: Search on S3 Using AWS Lambda
-
Show HN: Quickwit – OSS Alternative to Elasticsearch, Splunk, Datadog
Hi folks, Quickwit cofounder here.
We started Quickwit 3 years ago with a POC, "Searching the web for under $1000/month" (see HN discussions [0]), with the goal of making a robust OSS alternative to Elasticsearch / Splunk / Datadog.
We have reached a significant milestone with our latest release (0.7) [1], as we have witnessed users of the nightly version of Quickwit deploy clusters with hundreds of nodes, ingest hundreds of terabytes of data daily, and enjoy considerable cost savings.
To give you a concrete example, one company is ingesting hundreds of terabytes of logs daily and migrating from Elasticsearch to Quickwit. They divided their compute costs by 5x and storage costs by 2x while increasing retention from 3 to 30 days. They also increased their durability, accuracy with exactly-once semantics thanks to the native Kafka support, and elasticity.
The 0.7 release also brings better integrations with the Observability ecosystem: improvements of the Elasticsearch-compatible API and better support of OpenTelemetry standards, Grafana, and Jaeger.
Of course, we still have a lot of work to be a fully-fledged observability engine, and we would love to get some feedback or suggestions.
To give you a glance at our 2024 roadmap, we planned to focus on Kibana/OpenDashboard integration, metrics support, and pipe-based query language.
[0] Searching the web for under $1000/month: https://news.ycombinator.com/item?id=27074481
[1] Release blog post: https://quickwit.io/blog/quickwit-0.7
[2] Open Source Repo: https://github.com/quickwit-oss/quickwit
[3] Home Page: https://quickwit.io
- Show HN: Quickwit – OSS Alternative to Datadog, Elasticsearch
-
S3 Express Is All You Need
We tested S3 Express for our search engine quickwit[0] a couple of weeks ago.
While this was really satisfying on the performance side, we were a bit disappointed by the price, and I mostly agree with the article on this matter.
I can see some very specific use cases where the pricing should be OK but currently, I would say most of our users should just stay on the classic S3 and add some local SSD caching if they have a lot of requests.
[0] https://github.com/quickwit-oss/quickwit/
-
Show HN: Quickwit – Cost-Efficient OSS Search Engine for Observability
Hi HN, I’m one of the builders of Quickwit, a cloud-native OSS search engine for observability. As of 2023, we support logs and traces, metrics will come in 2024.
You know the pitch: while software like Datadog or Splunk are great, they often comes with hefty price tags. Our mission is to offer an affordable alternative. So we’ve built Quickwit, we’ve made it compatible with the observabilty ecosystem (OpenTelemetry, Jaeger, Grafana) and above all, we’ve made it cost-efficient / “easy” to scale (well it’s never easy to scale to petabytes..).
To give you a glance at the engine performance I made a benchmark on the GitHub Archive dataset, 23 TB of events, here are the main observations:
Indexing: costs $2 per ingested TB. With 4CPU, throughput is at 20MBs However, you'll observe > 30MB throughput on simpler datasets, like logs and traces.
Search: a typical query costs $0.0002 per TB (considering both CPU time and GET request costs). Using 8CPU, a simple query on 23TB is achieved in under a second.
Storage: on S3, it costs $8 per ingested TB per month on the GitHub Archive dataset. With logs and traces, you might see costs around $5/ingested TB due to a 2x better compression ratio.
I'm eager to get your thoughts on this!
Benchmark: https://quickwit.io/blog/benchmarking-quickwit-engine-on-an-...
Github repo: https://github.com/quickwit-oss/quickwit/
Website: https://quickwit.io/
- On S3, it costs $8 per ingested TB per month on the GitHub Archive dataset. With logs and traces, you might see costs around $4/ingested TB due to a 2x better compression ratio.
I'm eager to get your thoughts on this!
[0] Benchmark: https://quickwit.io/blog/benchmarking-quickwit-engine-on-an-...
- OSS Sub-second search and analytics engine on cloud storage
-
Ask HN: Who is hiring? (September 2023)
Quickwit (https://quickwit.io/) | Paris, France | Onsite and remote (based in Europe) | Full-time
The company is fully remote but we also have a small office in Paris. We prefer candidates based in Europe but can make exceptions for the right profiles.
- Senior Software Engineer 80-110k€ + 0.25-1% equity based on experience.
We’re looking for a senior software engineer to contribute to [Quickwit](https://github.com/quickwit-oss/quickwit), our open-source search and analytics engine. We have an ambitious roadmap for the next 18 months (performance optimization, distributed storage, support for SQL, query optimizer, revamp of our execution engine, etc.), and this is a great opportunity to shape the future of Quickwit while tackling fun and challenging problems in the field of distributed databases.
-
Observe your Rust application with Quickwit, Jaeger and Grafana
In our latest blog post, we walk you through the steps of instrumenting your Rust application and monitoring the performance on Grafana using Quickwit + Jaeger.
-
Quickwit 0.6.0 - Search and analytics on billions of logs with minimal hardware
Link: https://github.com/quickwit-oss/quickwit
What are some alternatives?
databend - 𝗗𝗮𝘁𝗮, 𝗔𝗻𝗮𝗹𝘆𝘁𝗶𝗰𝘀 & 𝗔𝗜. Modern alternative to Snowflake. Cost-effective and simple for massive-scale analytics. https://databend.com
MeiliSearch - A lightning-fast search API that fits effortlessly into your apps, websites, and workflow
openraft - rust raft with improvements
loki - Like Prometheus, but for logs.
s3s - S3 Service Adapter
elasticsearch-py - Official Python client for Elasticsearch
fluvio - Lean and mean distributed stream processing system written in rust and web assembly.
manticoresearch - Easy to use open source fast database for search | Good alternative to Elasticsearch now | Drop-in replacement for E in the ELK soon
dilbert-viewer - A simple comic viewer for Dilbert by Scott Adams
openobserve - 🚀 10x easier, 🚀 140x lower storage cost, 🚀 high performance, 🚀 petabyte scale - Elasticsearch/Splunk/Datadog alternative for 🚀 (logs, metrics, traces, RUM, Error tracking, Session replay).
storage - A vendor-neutral storage library for Golang: Write once, run on every storage service.
zincsearch - ZincSearch . A lightweight alternative to elasticsearch that requires minimal resources, written in Go.