News for hackers. Stuff that matters.
Re:Dear NoSQL: "SQL-isn't-scalable" is a lie by viraptor on Tuesday March 02, 2010 @08:47PM (#1163106)
Reading this article was a bit annoying. Right from the start: "I work in the financial industry [...] I worked in the insurance, telecommunication, and power generation industries." I was thinking only - you're not even supposed to look at nosql from that perspective - there's nothing for you there... just go away.

It doesn't support transactions and acid most of the time. There's no "we pay $xxxM for the support and blame you for everything" company in nosql products. It's not the same workload as you'd expect from kv/document-store used as a webpage backend.

One of the few serious "nosql" databases for enterprises like that is Berkeley DB - it's got what they need. I'm not sure why did he write that blog post... it just stated the obvious, but in form of a rant.

The funny thing though is - Berkeley DB is exactly what NoSQL is about... and it is used for local reliable storage in many big enterprises. Replication, logging, transactions, etc. - and it's just a kv-store really.

Re:Dear NoSQL: "SQL-isn't-scalable" is a lie by wvenable on Tuesday March 02, 2010 @09:47PM (#1163217)
I'm not sure why, these days, anyone would choose Berkeley DB over something like sqlite.
Re:Dear NoSQL: "SQL-isn't-scalable" is a lie by viraptor on Tuesday March 02, 2010 @10:27PM (#1163278)
BDB has proper transactions, provides the same type-safety as sqlite (i.e. none), doesn't have to go through abstractions like JDBC (overkill for sqlite), is backed by Oracle, has pure java implementation, has replication.

Sqlite has columns and can search based on them. It can also save you a couple of lines on manual joins. Does it provide something more?

(although tbh, I'd take Tokyo Tyrant over both of them - has columns, writer lock + server-side scripts instead of transactions, same model of replication as BDB)

Re:Dear NoSQL: "SQL-isn't-scalable" is a lie by Erwin on Wednesday March 03, 2010 @04:35AM (#1163772)
The berkeley interfaces that come out of the box with e.g. Python don't have any of the advanced features that the sqlite interface has, e.g. concurrent access. Any advanced usage of Berkeley DB is far more complex than sqlite, e.g. try opening a database so that multiple users can read/write it. With sqlite, no extra steps are necessary if you have an occasional separate process that needs to access the database (obviously it's not built for efficient concurrent access).

Ad-hoc SQL queries on the sqlite database are also a huge win. Much better than defining your own data structures and then tools to read/write them.

I don't know you mean by "proper" transactions. Sqlite has transactions for DML.