mimir VS sled

One of our top oss contributors is developing mimir as an embedded Meilisearch: https://github.com/GregoryConrad/mimir/tree/main/packages/mi...

I'm excited to announce the first stable release of mimir, a brand new Dart & Flutter NoSQL database!

Hey! I’m the author of Mimir (https://pub.dev/packages/mimir). I think it could deserve a spot on there 🙂!

I can’t help you with the gradle part. You’ll have to look up how to import AAR from local file system. I got it working with an ivy repo like this https://github.com/GregoryConrad/mimir/pull/89/files

I'm guessing you grabbed that milli_v1 part from mimir; if so, glad someone found it useful! :)

If you’re looking for an on-device database, Mimir can do all of those (minus geo-queries, but those can be easily added because the support needed for them is already there). https://pub.dev/packages/mimir (disclosure: I’m the author)

Take a look at mimir! It is a database that will do exactly want you want.

If you are looking for full-text search for your data (e.g., for a search bar in your app), I would recommend taking a look at mimir! Isar offers decent full-text search, but it is not typo-tolerant. mimir has typo-tolerant full-text search with 0 configuration necessary; simply add documents and search just works!

a few times, seems interesting. The author's also built a lot of other cool concurrency primitives for Rust as well.

[0] https://github.com/spacejam/sled

- Dropbox [3] uses a similar approach but they talk about it a bit more abstractly.

Sans-IO is more documented in Python [4], but str0m [5] and quinn-proto [6] are the best examples in Rust I’m aware of. Note that sans-IO is orthogonal to deterministic test frameworks, but it composes well with them.

With the disclaimer that my opinions are mine and mine alone, and don’t reflect the company I work at —— I do work at a rust shop that has utilized these techniques on some projects.

TigerBeetle is an amazing example and I’ve looked at it before! They are really the best example of this approach outside of FoundationDB I think.

[0]: https://risingwave.com/blog/deterministic-simulation-a-new-e...

[1]: https://risingwave.com/blog/applying-deterministic-simulatio...

[2]: https://dropbox.tech/infrastructure/-testing-our-new-sync-en...

[3]: https://github.com/spacejam/sled

[4]: https://fractalideas.com/blog/sans-io-when-rubber-meets-road...

[5]: https://github.com/algesten/str0m

[6]: https://docs.rs/quinn-proto/0.10.6/quinn_proto/struct.Connec...

Sled uses bw-tree actually https://github.com/spacejam/sled/wiki/sled-architectural-outlook

There is a valid argument to be made for threads over async in a large percentage of use cases where async is considered the default. If this is what you are referring to however, I don't think they ever referred to async as completely useless: https://github.com/spacejam/sled/issues/1123.

Have you looked into other pure-Rust databases as well, such as sled or GlueSQL which has an SQL interface on top of sled? I wonder how those would compare to Persy.

I'm not sure what you need. Are these of any use? https://github.com/meilisearch/heed https://github.com/spacejam/sled

There is also Sled but as I understand it that is being reworked to use the author's new DB core Marble

There are some databases like sled/FlashDB designed to be embedded to other applications even bare metal microcontrollers. But I do doubt the potential bussiness value of a pure embedded database.

https://github.com/spacejam/sled

To add transaction support, you probably need a good understanding of how the memtable works in Log Structured Merge trees: