@southpolesteve @rethinkdb Many.
-
-
Replying to @southpolesteve
@southpolesteve Pithy one would be: database choice depends on your data and what you need to do with it ;)1 reply 0 retweets 0 likes -
Replying to @southpolesteve
@southpolesteve@mathiasx and now I see I’ve duplicated matt’s response.1 reply 0 retweets 0 likes -
Replying to @devn
@devn@southpolesteve seriously, though, I've found there's a lot of factors to consider when you have a) >1 db server, b) schemaless store.2 replies 0 retweets 0 likes -
Replying to @mathiasx
@southpolesteve Read http://www.sarahmei.com/blog/2013/11/11/why-you-should-never-use-mongodb/ … until it sinks in how few data models are ideal for document store@devn1 reply 1 retweet 0 likes -
Replying to @mathiasx
@southpolesteve Now, Rethink does have relational joins but you're not going to have foreign keys.. so your app has to maintain those@devn1 reply 0 retweets 0 likes -
Replying to @mathiasx
@southpolesteve But for analytics data where I just had tons of records (100K or so) on a 8 node cluster, Rethink was good.@devn1 reply 0 retweets 0 likes -
Replying to @mathiasx
@southpolesteve It wasn't instantaneous and I likely wasn't tuning it perfectly but for that kind of stuff most queries aren't instant@devn2 replies 0 retweets 0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.