News for hackers. Stuff that matters.
Re:NoSQL Took Away The Relational Model And Gave Nothing Back by jbooth on Friday October 29, 2010 @04:49PM (#1848968)
What's the cost on that EMC array?

How many commodity servers could I buy for that?

I have a pretty solid idea what state of the art is in the RDBMS world - it's diminishing returns as a machine that's twice as powerful costs 10X as much, all the way up the enterprise ladder. It's spending 100k on your software licenses, 100k on your storage and 500 bucks on a CPU.

Not that there's anything wrong with that. It's ok. If your domain is highly transactional, it's probably a better move than implementing your own transactions over something else. Just don't pretend that your limitations are actually strengths -- you have your own strengths.

Re:NoSQL Took Away The Relational Model And Gave Nothing Back by gaius on Friday October 29, 2010 @05:03PM (#1849023)
It doesn't matter. You see, in business, there is no "cheap" or "expensive". There's worth the money, or not. It doesn't matter how many commodity servers I could buy for the cost; no matter how cheap they are, the money would be wasted if that simply the wrong technical approach.

Because you can't compete at this level by chucking increasing amounts of anything at the problem - people, dollars, spindles, nodes, you name it.

Re:NoSQL Took Away The Relational Model And Gave Nothing Back by jbooth on Friday October 29, 2010 @06:10PM (#1849259)
You see, in business, everything is about cheap or expensive. It's just a more broad definition that includes developer time and ROI.

If your problem is extremely transactional and legitimately unshardable, feel free to drop 6 mil on exadata. Or a half a mil on a database server and backup. But frankly, your objections are starting to have a religious feel to them. All I was saying is that PL/SQL is a pile of crap to code in and fundamentally unscalable without spending a boatload of money. A little better design can get the same thing with a lot less cash.

EDIT: No, those are facts, PL/SQL looks like it was designed in 1965 and, yes, putting all of your CPU processing into a single node is fundamentally unscalable. I've seen it. It was fundamentally unscalable.

I'm not making a religious point about RDBMS - it can be the best model in many situations. I'm making a point about single bottlenecks for your architecture.

Re:NoSQL Took Away The Relational Model And Gave Nothing Back by gaius on Friday October 29, 2010 @06:45PM (#1849369)
"pile of crap" and "fundamentally unscalable" and I'm the religious one o_0
Re:NoSQL Took Away The Relational Model And Gave Nothing Back by ora600 on Friday October 29, 2010 @10:05PM (#1849847)
BTW. All architectures have a single bottleneck. Thats pretty much by definition.

Oracle tried to market their Exalogic as "no bottlenecks" which is nearly as funny as "unbreakable linux" and "zero latency".

Re:NoSQL Took Away The Relational Model And Gave Nothing Back by cosmicray on Friday October 29, 2010 @05:17PM (#1849085)
You buy the EMC unit, because you want the EMC tech to call you and say "we see you have a failing drive, I'm en-route, and I'll be there in 15 minutes with a replacement". Even if you are not paying attention, the unit called in and told the control center it needed attention.