Sunday, March 23, 2014

Weekly Update

Note: I usually receive notifications of comments to my posts, which I then publish if they are not spam. Today, however, I noticed a whole bunch of old comments that were waiting for moderation, some of 2013, of which I was not notified. I have just published them and replied. Apologies to the commenters.

1. Quote of the Week
Schemaless describes the storage engine, not the data. Data has schema. No Data is ever Schemaless. Schemaless DBs merely describe a feature of themselves, not the data they store. Namely that they don't store and enforce this schema in addition to the data.
One advantage of this Is that you can change the schema "easily" - helps with up time. Now if you don't evolve the old data with each schema change you can end up with multiple schemas stored in your backend and no way of knowing which data is of which schema without some form of analysis of the data. Show me the Front end that can deal with evolving schemas without knowing about them ;) Point being Schema's always there wether any tier deals with it explicitly or not. Something has to manage it.
2. To Laugh or Cry?
Big data means the reign of the relational database is over
3. Online
What is the best way to explain Normalization 1NF,2NF and 3NF
4. And now for something completely different
Samsung’s entire leadership team is paid less than individual executives at Google, Apple

Do you like this post? Please link back to this article by copying one of the codes below.

URL: HTML link code: BB (forum) link code:


  1. I just came across the following quote in MATHEMATICS WRITTEN IN SAND by William Kahan (1983). Kahan was the driving force behind the IEEE floating point standard and fights the ongoing good fight against ignorance and misconceptions re numerical computation.

    "Anomalies generally undermine economical thought,
    thereby undermining the integrity of software and
    inflating its cost. The worst anomalies can be
    kept out of computers. When they do intrude they
    are not always accidental; too often they follow
    from design decisions induced by misconceptions
    widely taught as rules of thumb about what to
    neglect in approximate computation. Refutations
    of those misconceptions abound in the literature
    but cannot help someone who has
    not read them, who believes every elementary
    subject must be obvious, and whose mathematical
    experience is too narrow to support sound
    judgments. Here is another domain where our
    failure to teach mathematics effectively to a
    past generation comes home to roost."


  2. A culture pervades the entire society and there are very rare and limited exceptions, if any.