ethangunderson

5 ms·

1.
by ethangunderson 4y ago
Hi, software developer at Cars.com here. While I appreciate the ego boost of thinking that we're somehow better than average, I don't believe this to be true. You can get away with sloppy Elixir code just as easily as you can in P
2.
by ethangunderson 15y ago
Comparing map/reduce in Mongo and Couch is really apples and oranges. They are designe to do two different things. i.e data processing vs building views. Mongo is designed from the ground up to deal with large datasets. Take a look at their
3.
by ethangunderson 15y ago
Full text of their post: https://gist.github.com/fb41d5002822fff18686
4.
by ethangunderson 15y ago
Damn, didn't realize you had to be logged in to see the posting about it.
5.
Ravelry.com hacked - user information leaked(ravelry.com)
4 points by ethangunderson 15y ago|4 comments
6.
by ethangunderson 15y ago
When we talk about consistency, we're talking about taking the database from one consistant state to another. With replica sets, we're still only dealing with one master. We can get inconsistant reads from the replicas, but we're always wri
7.
by ethangunderson 15y ago
If they're doing the same thing, that's just as shitty. But I've been meaning to listen to that episode of the Changelog for awhile now, so thanks for the reminder!
8.
by ethangunderson 15y ago
Basho has always had an issue with the way Mogno was architected and marketed, and they have no issue with letting people know. (several blog posts, killdashnine parties) I actually like both Mongo and Riak. I think they both solve a differ
9.
by ethangunderson 15y ago
It was a thinly veiled bash on Mongo.
10.
Groupon Now(groupon.com)
8 points by ethangunderson 15y ago|0 comments
11.
by ethangunderson 16y ago
Software engineering is a subset of programming, particularly the subset where people give a shit about the code they ship.
12.
by ethangunderson 16y ago
The issue with that is if your DB gets backed and starts queuing writes, the timestamps will be skewed. Obviously this isn't always a show stopper, but a caveat nonetheless.
13.
by ethangunderson 16y ago
The first item in the list really bugs me. It's not enough to just tell me not to do something, teach me why it's bad. That way, I can explain to others why this is a mistake instead of just regurgitating the same explanation of 'it's a per
14.
by ethangunderson 16y ago
It's worth noting that Twitter has built a lot on top of MySQL to get to the scale they're at. Take FlockDB for example, https://github.com/twitter/flockdb So I guess that statement should be written as "you can't scale with just those"
15.
by ethangunderson 16y ago
FWIW, Foursquare's situation was kind of unique. They have a need for all of their data to be in RAM. In most applications, you can define a working set of data. As long as you can keep that working set and indexes in RAM, you'll be fine.
16.
by ethangunderson 16y ago
Just like most things, it's not that simple. For example... Cassandra is good for 'big data' if you're ok dealing with the repercussions of eventual consistency, and questionable performance characteristics. Not to mention the mediocre comm
17.
by ethangunderson 16y ago
It's also missing a bunch of the conversation, making it rather worthless.
18.
by ethangunderson 16y ago
Is there a NoSQL database that claims that? I don't know of one. Rather, they attempt to implement different facets of CAP. Also, the CAP theorem, as it stands, is showing its age, Brewer himself has said it needs to be updated.
19.
by ethangunderson 16y ago
No system could prevent it, but there are databases(Oracle and MongoDB off the top of my head, and I'm sure there are others) that implement slave delays specifically to help mitigate human error like this.
20.
by ethangunderson 16y ago
Thanks for pointing that out, it's been fixed.
21.
by ethangunderson 16y ago
The idea should be that you are picking the right tool for the job. Just because you could just use Postgres, doesn't mean that another data store wouldn't be better suited for your problem space. Could be Mongo, could be Cassandra, it very
22.
by ethangunderson 16y ago
Interesting, I didn't know that priority was given to reads(in theory anyways). Thanks for the tip! As for server durability, yes, it has been beaten to death. Yet, I still talk to developers that either have no idea that's how Mongo operat
23.
by ethangunderson 16y ago
One of the best things to come out the nosql 'movement' is exactly that, no more silver bullets. As much as I like Mongo, I would never blindly recommend it, or any other data store for that matter. It's all about analyzing what your proble
24.
Two Reasons You Shouldn't Use MongoDB(ethangunderson.com)
76 points by ethangunderson 16y ago|26 comments
25.
Ringo-evented - a JVM based alternative for Node.js built on Netty(github.com)
3 points by ethangunderson 16y ago|0 comments
26.
by ethangunderson 16y ago
This used to be the case in earlier versions, but now it only issues a server level write lock for atomic updates, reads can still happen. It's not ideal, but it is an improvement.