Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How we replaced Elasticsearch and MongoDB with Rust and RocksDB

radar.com

Post reply on HN
Print view View original

71–80 of 104 posts

Re: How we replaced Elasticsearch and MongoDB with Rust and RocksDB

#71

Post by maxboone »

atombender wrote: post #42
brunohaid wrote: post #14

Bit thin on details and not looking like they’ll open source it, but if someone clicked the post because they’re looking for their “replace ES” thing: Both https://typesense.org/ and https://duckdb.org/ (with their spatial plugin) are excellent geo performance wise, the latter now seems really production ready, especially when the data doesn’t change that often. Both fully open source including clustered/sharded setu…

DuckDB does not have any kind of sharding or clustering? It doesn't even have a server (unless you count the HTTP Server Extension)?

Motherduck is the spin-off from DuckDBthat does that. But there's also: https://duckdb.org/2025/05/27/ducklake.html

You can also attach DuckDB to Apache Flight which will make it work beyond local operation.

Re: How we replaced Elasticsearch and MongoDB with Rust and RocksDB

#72

Post by benjiro »

feverzsj wrote: post #68

Sounds like all they need is Postgres or just Sqlite.

Yep, their goal was to use a monolite solution, instead of a clustered elasticsearch.

Postgres + pg_search (= tantivy) will have gotten them there for 80%. Sure, postgres really needs a plugin storage engine for better SSD support (see orioledb).

But creating your own database for your own company, is just silly.

There is a lot of money in the database market, and everybody wants to do their own thing to tied customers down to those databases. And that is their main goal.

Re: How we replaced Elasticsearch and MongoDB with Rust and RocksDB

#73

Post by victorbjorklund »

pianoben wrote: post #60

Lol I "love" that the first benefit this company lists in their jobs page is "In-Office Culture". Do people actually believe that having to commute is a benefit ?

Some people like being in office. People are different.

Re: How we replaced Elasticsearch and MongoDB with Rust and RocksDB

#74

Post by aflag »

pianoben wrote: post #60

Lol I "love" that the first benefit this company lists in their jobs page is "In-Office Culture". Do people actually believe that having to commute is a benefit ?

I rather commute than WFH. So yeah, people do. Maybe not all the people, but certainly some people.

Re: How we replaced Elasticsearch and MongoDB with Rust and RocksDB

#75

Post by nchmy »

mdaniel wrote: post #55
nchmy wrote: post #40

Earlier quoted context omitted.

Check out manticoresearch - it's older than Lucene (which elasticsearch is built on), faster and simpler.

GPLv3 https://github.com/manticoresoftware/manticoresearch/blob/13...

Are you running customized, or even embedded, versions of your search engine? Highly doubtful. So, GPL is irrelevant. Just run it and interface with it via api.

Re: How we replaced Elasticsearch and MongoDB with Rust and RocksDB

#76

Post by porridgeraisin »

jjordan wrote: post #18
brunohaid wrote: post #14

Bit thin on details and not looking like they’ll open source it, but if someone clicked the post because they’re looking for their “replace ES” thing: Both https://typesense.org/ and https://duckdb.org/ (with their spatial plugin) are excellent geo performance wise, the latter now seems really production ready, especially when the data doesn’t change that often. Both fully open source including clustered/sharded setu…

Typesense is an absolute beast, and it has a pretty great dev experience to boot.

Can you share what makes it better than competitors? And what's great about the dev experience? Did you use their cloud offering? The marketing material looks great, but I want to hear a user's experience.

Re: How we replaced Elasticsearch and MongoDB with Rust and RocksDB

#77

Post by hyc_symas »

maelito wrote: post #2

I wonder if this could help Photon, the open source ElasticSearch/OpenSearch search engine for OSM data. It's a mini-revolution in the OSM world, where most apps have a bad search experience where typos aren't handled. https://github.com/komoot/photon

A system built on LMDB will work better for this use case than RocksDB. And OSM Express already uses it. https://wiki.openstreetmap.org/wiki/OSM_Express

Re: How we replaced Elasticsearch and MongoDB with Rust and RocksDB

#78

Post by PepsiCola »

LtWorf wrote: post #64
nickm12 wrote: post #63

Earlier quoted context omitted.

You can't reduce the in-office or remote experience purely to commuting. It's just one aspect about how and where you work and work life balance in general. But since you asked, yes, I actually enjoy commuting when it is less than 30 minutes each way and especially when it involves physical activities. My best commutes have been walking and biking commutes of around 20-25 minutes each way. They give me exercise, a ch…

[flagged]

Or maybe they don't live in US where everything is by car :)

Re: How we replaced Elasticsearch and MongoDB with Rust and RocksDB

#80

Post by WASDx »

unsuitable wrote: post #31
mikeocool wrote: post #8

Earlier quoted context omitted.

In my experience, the care and feeding that goes into an Elastic Search cluster feels like it's often substantially higher than that involved in the primary data store, which has always struck me as a little odd (particularly in cases where the primary data store is an RDBMS). I'd be very happy to use simpler more bulletproof solutions with a subset of ES's features for different use cases.

In my experience Elastic Search lacks fundamental tooling, like a CLI that copies data between nodes.

The `/_cluster/reroute` endpoint lets you do that with a curl. We have aliases for common operations so I've never felt that I lack a CLI. I'm happy with Elasticsearch overall having a few years of experience.
Post reply on HN