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

We use RethinkDB

blog.workshape.io

Post reply on HN
Print view View original

21–30 of 78 posts

Re: We use RethinkDB

#21

Post by coffeemug »

tracker1 wrote: post #14
felipesabino wrote: post #6

From RethinkDB docks [1], I am still a bit confused how this locking system works for read/write and also a bit skeptical regarding their claim that 'in most cases writes can be performed essentially lock-free'. I am using MongoDB and didn't have many issues when my databases had 120,000 documents either, the problem began when we hit the millions... The combination of write locks and our need for dynamic queries (me…

FYI, with MongoDB, just because you can't and shouldn't index everything, doesn't mean you can't have any indexes... if your most common fields bring your queries down, they're still pretty helpful. I actually really like where RethinkDB is headed, and within the year most of my issues should be resolved. Another couple databases to consider, depending on your needs would be ElasticSearch and Cassandra... it reallly…

Could you list your issues with Rethink? It would really help for product prioritization.

Re: We use RethinkDB

#22

Post by simi_ »

I've been using/following RethinkDB since I started as Lavaboom's CTO. It's been a smooth ride so far, and the occasional perf improvements are always welcome. Some aspects of the database are especially lovely, like the web admin or painless deployments of new nodes, especially if you're using Docker.

Shameless plug (we've just went open sourced most of our services): https://www.lavaboom.com/

Re: We use RethinkDB

#23

Post by tracker1 »

coffeemug wrote: post #21
tracker1 wrote: post #14

Earlier quoted context omitted.

FYI, with MongoDB, just because you can't and shouldn't index everything, doesn't mean you can't have any indexes... if your most common fields bring your queries down, they're still pretty helpful. I actually really like where RethinkDB is headed, and within the year most of my issues should be resolved. Another couple databases to consider, depending on your needs would be ElasticSearch and Cassandra... it reallly…

Could you list your issues with Rethink? It would really help for product prioritization.

As mentioned in another thread, automagic failover the one still pending, and geospatial indexes/searches (now in the product).

It's wild how many options there are that tailor themselves to all kinds of data out there.

Re: We use RethinkDB

#25

Post by TylerE »

coffeemug wrote: post #16
kolencherry wrote: post #9

We use RethinkDB in production and our main frustration lies around the lack of automatic failover. We're looking forward to 2.0, which is supposed to bring automatic failover (using Raft for consensus) to RethinkDB.

Slava @ RethinkDB here. Unfortunately automatic failover won't be a part of 2.0, but it will happen very quickly after that. Please hang in there, we expect to ship this feature some time in May. I just saw a demo of the failover feature yesterday from Tim Maxwell (the lead engineer on this), and it's really impressive! Another side benefit of this feature is live reshards -- you'll be able to reshard/rebalance data…

You guys are killing it. Wish I had a product I could write around rethink....currently at the day job our stuff is mostly Mongo....all layered under django-nonrel with lots of mongo crud so a port wouldn't really be an option I don't think.

Re: We use RethinkDB

#26

Post by habitue »

jamescostian wrote: post #8

+1 to using RethinkDB! I'm also using RethinkDB in production, and I love it! The only issue is that you have to set up persistent filters via iptables in addition to having an authKey. They do have a guide[0] for that, however they do not provide any instructions for ensuring that the filters on iptables stay up, or how to restore them if they are temporarily wiped out :/ [0] http://rethinkdb.com/docs/security/

I created an issue for this on our docs repo[0]. Thanks for the feedback!

[0]https://github.com/rethinkdb/docs/issues/674

Re: We use RethinkDB

#27

Post by nightski »

hiphipjorge wrote: post #20
lewisjoe wrote: post #4

I've always wondered what's the best way to integrate a database engine with the application. 1) Use a middleware/ORM/Whatever which abstracts away the query-lang of the db, and provides a pluggable multi-db support 2) Just use native db query language with all exclusive features of the engine. Companies like workshape.io, why do they prefer the latter?

Well, here's where the difference between query builders and ORMs comes in. Query builders (usually integrated with ORMs) are usually used by people who don't want to write any SQL. SQL is very performant and powerful, but not that easy to understand or write. This is especially so when you think about the context switch between programming languages and SQL. The advantage of some of the NoSQL databases (MongoDB and…

I disagree. I use ORMs/Query Builders for two reasons (even if deeply familiar with SQL syntax and semantics).

1. Dynamic queries for reporting purposes. Is it possible to hand roll this with SQL string concat for every query? Yes. Some of us value time and correctness.

2. Type safety/Refactoring and change management. Sure even a Query Builder/ORM model doesn't know if it matches the production database at compile time. But when your database does change and you need to update the model to match it then it is a lot easier to do a refactoring on the record than to manually update every SQL query string where that table is involved and hope there isn't a missing test or invalid query out there which will now be broken.

Re: We use RethinkDB

#28

Post by bbcbasic »

emergentcypher wrote: post #5

Why is it so trendy these days to say that everything was built "with love"?

It's just a meme.

Like it is also trendy to have an over-sized picture of young people working on wooden desks in an industrial-chic office taking up 70% of the screen space.

Goes nicely with the Bootstrap template, Lobster font, Circular cropped photos of founders, Ping pong tables, Ruby on Rails. Etc. Etc.

Re: We use RethinkDB

#29

Post by jefficient »

coffeemug wrote: post #21
tracker1 wrote: post #14

Earlier quoted context omitted.

FYI, with MongoDB, just because you can't and shouldn't index everything, doesn't mean you can't have any indexes... if your most common fields bring your queries down, they're still pretty helpful. I actually really like where RethinkDB is headed, and within the year most of my issues should be resolved. Another couple databases to consider, depending on your needs would be ElasticSearch and Cassandra... it reallly…

Could you list your issues with Rethink? It would really help for product prioritization.

Are unique indexes planned for any of the upcoming releases?

Re: We use RethinkDB

#30

Post by [deleted] »

tracker1 wrote: post #23
coffeemug wrote: post #21

Earlier quoted context omitted.

Could you list your issues with Rethink? It would really help for product prioritization.

As mentioned in another thread, automagic failover the one still pending, and geospatial indexes/searches (now in the product). It's wild how many options there are that tailor themselves to all kinds of data out there.

[deleted]
Post reply on HN