Solved

Azure DocumentDB vs Azure SQL

Posted on 2014-10-08
6
483 Views
Last Modified: 2015-05-11
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).
0
Comment
Question by:RXGeorge
  • 2
6 Comments
 
LVL 19

Assisted Solution

by:Peter Hutchison
Peter Hutchison earned 250 total points
ID: 40368416
I am not familiar with DocumentDB or NoSql.
But say you left the company, is there anyone who could easily take over the project and maintain it, compared to someone with just SQL experience?
0
 
LVL 42

Accepted Solution

by:
pcelba earned 250 total points
ID: 40368484
You have to decide what is your need and intention. The venture for next 10+ years is suitable for both solutions.

Your concerns are similar to mine.

SQL Server is here for long time so it means the proof of feasibility and reliability. It supports everything you need incl. BLOB data storage and fulltext indexes.

DocumentDB is something new and neither you nor Microsoft knows about its future. To vote for DocumentDB now shows just the fact you like to implement new things or you have some vision. NoSQL is a new trend and next 10 years will show if your decision was right or not... Microsoft can stop DocumentDB development at any point as they did for other products in the past. SQL will be here for a long time.

I would wait with DocumentDB but that's my nature. I am using on-line services just for backup purposes.
0
 

Author Comment

by:RXGeorge
ID: 40370735
The kid in me wants to go DocumentDB - it;d be fun.  The grown-up side, however, fears that even with ongoing Microsoft support and maintainance - i will be isolated.  Everytime i want to run a report or use some other ad-hoc tool, It will not be supported on DocumentDb and would have been on Azure SQL.
0
 
LVL 42

Expert Comment

by:pcelba
ID: 40370764
OTOH, this is a question of the backend. The frontend may be designed to support more different backends and the effort to switch from one to another should not mean big amount of work then...
0

Featured Post

Master Your Team's Linux and Cloud Stack

Come see why top tech companies like Mailchimp and Media Temple use Linux Academy to build their employee training programs.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

These days, all we hear about hacktivists took down so and so websites and retrieved thousands of user’s data. One of the techniques to get unauthorized access to database is by performing SQL injection. This article is quite lengthy which gives bas…
Or at least that’s the word according to a new blog from Tech Target on AWS’s new Managed Services (MS) offering. According to the blog, AWS is launching their AWS MS program to expedite the adoption of cloud by Fortune 1000 and Global 2000 companie…
Viewers will learn how to use the SELECT statement in SQL and will be exposed to the many uses the SELECT statement has.
Viewers will learn how to use the UPDATE and DELETE statements to change or remove existing data from their tables. Make a table: Update a specific column given a specific row using the UPDATE statement: Remove a set of values using the DELETE s…

837 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question