differential-dataflow
Typesense
differential-dataflow | Typesense | |
---|---|---|
14 | 129 | |
2,473 | 17,965 | |
0.8% | 2.7% | |
8.3 | 9.8 | |
7 days ago | 7 days ago | |
Rust | C++ | |
MIT License | GNU General Public License v3.0 only |
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.
differential-dataflow
-
We Built a Streaming SQL Engine
Some recent solutions to this problem include Differential Dataflow and Materialize. It would be neat if postgres adopted something similar for live-updating materialized views.
https://github.com/timelydataflow/differential-dataflow
https://materialize.com/
-
Hydroflow: Dataflow Runtime in Rust
I'm looking for this but can't find it, how does this project compare to differential dataflow?
As a sibling commenter mentioned, it's built on timely dataflow (which is lower-level), but that already has differential dataflow[0] built on top of it by the same authors.
How do they differ?
[0]: https://github.com/TimelyDataflow/differential-dataflow
- Using Rust to write a Data Pipeline. Thoughts. Musings.
- PlanetScale Boost
- Program Synthesis is Possible (2018)
-
Convex vs. Firebase
hi! sujay from convex here. I remember reading about your "reverse query engine" when we were getting started last year and really liking that framing of the broadcast problem here.
as james mentions, we entirely re-run the javascript function whenever we detect any of its inputs change. incrementality at this layer would be very difficult, since we're dealing with a general purpose programming language. also, since we fully sandbox and determinize these javascript "queries," the majority of the cost is in accessing the database.
eventually, I'd like to explore "reverse query execution" on the boundary between javascript and the underlying data using an approach like differential dataflow [1]. the materialize folks [2] have made a lot of progress applying it for OLAP and readyset [3] is using similar techniques for OLTP.
[1] https://github.com/TimelyDataflow/differential-dataflow
[2] https://materialize.com/
[3] https://readyset.io/
-
Announcing avalanche 0.1, a React- and Svelte-inspired GUI library
differential dataflow which is used to power materialize db
-
Differential Datalog
It's partially inspired by Linq, so the similarity you see is expected.
It's not really arbitrary structures so much, though you're mostly free in what record type you use in a relation (structs and tagged enums are typical, though).
The incremental part is that you can feed it changes to the input (additions/retractions of facts) and get changes to the outputs back with low latency (you can alternatively just use it to keep an index up-to-date, where you can quickly look up based on a key (like a materialized view in SQL)).
This [0] section in the readme of the underlying incremental dataflow framework may help get the concept across, but feel free to follow up if you're still not seeing the incrementality.
[0]: https://github.com/TimelyDataflow/differential-dataflow#an-e...
- Dbt and Materialize
- Materialized view questions
Typesense
-
Website Search Hurts My Feelings
There are actually plenty of non-ES products that are way easier to integrate and tune (and get better results with less effort).
- Typesense (https://github.com/typesense/typesense)
- Algolia
- Google Programmable Search Engine (https://programmablesearchengine.google.com/about/)
- Remote Machine Learning and Searching on a Raspberry Pi 5
-
Open Source alternatives to tools you Pay for
Typesense - Open Source Alternative to Algolia
-
DNS record "hn.algolia.com" is gone
If you like your penny take a look at Typesense https://typesense.org/ - nothing to complain here. Especially nothing complain about pricing.
-
Vector databases: analyzing the trade-offs
I work on Typesense [1] (historically considered an open source alternative to Algolia).
We then launched vector search in Jan 2023, and just last week we launched the ability to generate embeddings from within Typesense.
You'd just need to send JSON data, and Typesense can generate embeddings for your data using OpenAI, PaLM API, or built-in models like S-BERT, E-5, etc (running on a GPU if you prefer) [2]
You can then do a hybrid (keyword + semantic) search by just sending the search keywords to Typesense, and Typesense will automatically generate embeddings for you internally and return a ranked list of keyword results weaved with semantic results (using Rank Fusion).
You can also combine filtering, faceting, typo tolerance, etc - the things Typesense already had.
[1] https://github.com/typesense/typesense
[2] https://typesense.org/docs/0.25.0/api/vector-search.html
-
Creating an advanced search engine with PostgreSQL
For something small with a minimal footprint, I'd recommend Typesense. https://github.com/typesense/typesense
-
Obsidian Publish full text search
I haven’t used Publish, but I’d assume you could use something like https://typesense.org/ to index and search the vault.
-
DynamoDB search options
A cheaper option would be to use https://typesense.org. You can use DynamoDb streams to automatically load records. It has worked well for me.
-
[Guide] A Tour Through the Python Framework Galaxy: Discovering the Stars
Try tigris | typesense for faster search
-
Is it worth using Postgres' builtin full-text search or should I go straight to Elastic?
I’m also checking out Typesense as a possibility for replacing Elastic: https://typesense.org/
What are some alternatives?
ballista - Distributed compute platform implemented in Rust, and powered by Apache Arrow.
MeiliSearch - A lightning-fast search API that fits effortlessly into your apps, websites, and workflow
materialize - The data warehouse for operational workloads.
Elasticsearch - Free and Open, Distributed, RESTful Search Engine
reflow - A language and runtime for distributed, incremental data processing in the cloud
Apache Solr - Apache Lucene and Solr open-source search software
differential-datalog - DDlog is a programming language for incremental computation. It is well suited for writing programs that continuously update their output in response to input changes. A DDlog programmer does not write incremental algorithms; instead they specify the desired input-output mapping in a declarative manner.
meilisearch-laravel-scout - MeiliSearch integration for Laravel Scout
timely-dataflow - A modular implementation of timely dataflow in Rust
loki - Like Prometheus, but for logs.
clj-3df - Clojure(Script) client for Declarative Dataflow.
sonic - 🦔 Fast, lightweight & schema-less search backend. An alternative to Elasticsearch that runs on a few MBs of RAM.