Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

That's delivery. User accounts, network encryption and Windows support.

I did a couple of interviews with this people; and I can ensure this features have a few thoughts behind them.

Happy to see RethinkDB going on, and very sad I didn't make 100% my best at the interviews by personal issues at the time.

It's a pity that many people here in my country do not know still about RethinkDB. Other mainstream databases are more common knowledge.

I wish the best for you, and I keep a very good impression of each and every one of the people with whom I could talk at the process.

Very curious about the windows port. Has been hard? do you use any kind of framework that did ease the porting of the RethinkDB code?

Network encryption is undervalued in this times. A funny and serious feature. I would like to see the dashboards, thoughts and meetings around this one.

Keep up the good job!



* It's a pity that many people here in my country do not know still about RethinkDB. Other mainstream databases are more common knowledge. *

I guess is because this guys have been jumping around to see what sticks, their focus nows seems to be the "the database for the realtime web".

Why should companies bother if rethinkdb doesn't show to have clear goals yet? tomorrow they can be the "database for the (whatever)".


If I remember my RethinkDB history correctly, they picked the realtime web as their focus a while back.

Also, RethinkDB has kept their focus on real-time use cases since picking this focus.


I've heard about RethinkDB for the first time in 2013[1] and at the time it was described as "MongoDB with joins and auto-sharding".

I also heard that one of the initial "killer-features" of RethinkDB was supposed to be a stored history, just like a big persistent data structure (in my understanding, similar to Datomic). In the video[2] a lot of time was spent describing the benefits of an append-only structure.

[1]: https://www.youtube.com/watch?v=H9G1dCMTWps [2]: https://www.youtube.com/watch?v=uDHc3lkr3Ns


> "MongoDB with joins and auto-sharding"

It still is that. And (now) more.

I don't think it was ever supposed to be a history-saving data structure -- that log-structured stuff is (I haven't watched the video, I'm assuming) about talking nice to SSD's. It was at one point, after that video, a single-machine memcache-compatible persistent key/value store, before the pivot to being clustered and having its own query API.


What exactly what their previous goal? I thought they've always been for real-time search, at least that was the moniker when I looked at it 1 year previous.




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: