Azure DocumentDB vs Azure SQL
Posted on 2014-10-08
There is an old saying - "If the only tool you have is a hammer, every problem looks like a nail". I am starting a new project and i don't want to make that mistake. I have abundant experience building SQL based systems and have grown comfortable with SQL Server specifically. But this project will be hosted in Azure. I was planning to use Azure SQL to store the data. I understand that i may be looking at it myopically, but the data seems (to me) to fit naturally into TABLES. If this were 5 years ago, i would not even have this internal debate. But then i looked at DocumentDB.
DocumentDB programming model seems nice and clean (C# serialization/deserialization) and that makes my code nice and i start to drool. I felt myself being lured in by the bright shiny new thing. If this (NoSQL) is the future (and it may be), i don't want to be starting a new project with my grand-dad's database ;-)
First and foremost, this new project is a new business venture for my company. If successful, it will be around for 10 years or more. My data requirements are not HUGE. I don't need petabytes. The AzureSQL limits seem to be acceptable to me. DocumentDB is appealing but new and missing many things i "MAY" need. Sure, they may come along over time, but that is a gamble. But the siren song of NoSQL is pulling me in and i need a sanity check.
Please provide me your thoughts on this question (Sobering slaps across the face accepted).