No No No: The Curiously Absent Architecture of Postmodern Analytic Databases

Some say architecture is destiny. But it seems as if the world of analytic databases is moving on many fronts in all directions with no particular destination. That, in fact, is probably a good working definition of “postmodern.”

That’s the only reasonable conclusion you can draw from the sprawling mess of a movement known as “NoSQL.” It defines itself by what it is not, which would be easy to do if all it were rebelling against were something well-defined, such as the need to use Structured Query Language (SQL) to access, query, update, and manipulate data, or the need to store and manage that data in third-normal-form relational databases.

But no.  The NoSQL movement seems to fancy itself a catchall for all things “next-generation database,” though even there it is not clear what exactly they’re rebelling against. Check out this “NoSQL” scoping definition on the movement’s principal website: “Next Generation Databases [are] non-relational, distributed, open-source...horizontally scalable... modern web-scale databases....schema-free, replication support, easy API, eventual consistency, and more.”

Whew! If that non-definition didn’t leave you gasping for breath, the unruly menagerie of “No SQL” database approaches listed on the website will completely rob you of your oxygen supply. Apparently, this movement includes an unholy host of old and new database approaches, including wide column store/ column families, document store, key value/ tuple store, eventually consistent key value store, graph databases, object databases, grid database solutions, and XML databases.

Read more

Number of people using BI

By Boris Evelson


A number of clients ask me "how many people do you think use BI". Not an easy question to answer, will not be an exact science, and will have many caveats. But here we go:


  1. First, let's assume that we are only talking about what we all consider "traditional BI" apps. Let's exclude home grown apps built using spreadsheets and desktop databases. Let's also exclude operational reporting apps that are embedded in ERP, CRM and other applications.
  2. Then, let's cut out everyone who only gets the results of a BI report/analysis in a static form, such as a hardcopy or a non interactive PDF file. So if you're not creating, modifying, viewing via a portal, sorting, filtering, ranking, drilling, etc, you probably do not require a BI product license and I am not counting you.
  3. I'll just attempt to do this for the US for now. If the approach works, we'll try it for other major regions and countries.
  4. Number of businesses with over 100 employees (a reasonable cut off for a business size that would consider using what we define as traditional BI) in the US in 2004 was 107,119
  5. US Dept of Labor provides ranges as in "firms with 500-749 employees". For each range I take a middle number. For the last range "firms with over 10,000" I use an average of 15,000 employees.
  6. This gives us 66 million (66,595,553) workers employed by US firms who could potentially use BI
  7. Next we take the data from our latest BDS numbers on BI which tell us that 54% of the firms are using BI which gives us 35 million (35,961,598) workers employed by US firms that use BI
Read more