You took a real beating on your blog, which prompted my edit.
It may be useful at times to frame the debate in terms of time to market, secondary apps, etc. The relational model necessarily presupposes you will use the database for more than one thing, and over an extended period of time, thus warranting a high up-front investment and agnostic model. This may be right in some cases, but often times it's more important to publish early, bootstrap yourself, and start iterating.
Thanks. Didn't expect as much interest as I got - would definitely have worked longer on the post if I thought thousands of people would have read it :)
My view is not that relational is bad, but that the world needs an alternative.
Comments
You took a real beating on your blog, which prompted my edit.
It may be useful at times to frame the debate in terms of time to market, secondary apps, etc. The relational model necessarily presupposes you will use the database for more than one thing, and over an extended period of time, thus warranting a high up-front investment and agnostic model. This may be right in some cases, but often times it's more important to publish early, bootstrap yourself, and start iterating.
Thanks. Didn't expect as much interest as I got - would definitely have worked longer on the post if I thought thousands of people would have read it :)
My view is not that relational is bad, but that the world needs an alternative.