nosql vs relational database

  • sqlcool

    SSC Eights!

    Points: 967

    Hello Gurus

    I am a SQL-Server developer + Development DBA (Production DBA is managed by our hosting partner)

    While i was surfing the web, I came across NoSQL article (Link below). Is this something relational database guys has to be concerned about? I am concerned on what future holds for SQL-Developers and SQL-server DBAs

    Any thoughts gurus?

    http://techblog.netflix.com/2011/01/nosql-at-netflix.html

    http://en.wikipedia.org/wiki/NoSQL

    Cheers

  • Grant Fritchey

    SSC Guru

    Points: 396560

    It really depends on the business. There are places where nosql is going to, rightly, kick out OLTP systems. There are places where nosql does not belong. Just as an example, I really, really don't want my banking to be done with eventual consistency.

    ----------------------------------------------------
    The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood...
    Theodore Roosevelt

    The Scary DBA
    Author of: SQL Server 2017 Query Performance Tuning, 5th Edition and SQL Server Execution Plans, 3rd Edition
    Product Evangelist for Red Gate Software

  • Jeremiah Peschka

    SSChasing Mays

    Points: 610

    I'd suggest that you stop worrying about losing your job to something new and instead pioneer that something new. Relational databases aren't going anywhere, but they are no longer the only game in town. Non-relational databases have a lot of strengths and weaknesses that allow the to complement the strengths and weaknesses of the RDBMS.

    While you don't want your banking to be done with eventual consistency, it's most likely not being done with ACID transactions. Huge banks are typically going to dump your daily transactions in some kind of queue for processing at some later time. It's just not possible to easily and cheaply get the kind of throughput that we demand when you're dealing with transactions from millions of individual customers plus mortgages and commercial customers.

    Besides, with a properly designed eventually consistent system it's probably going to be faster and more error proof than a single server set up. Eventually consistent systems are, typically, "eventually" consistent over the period of several milliseconds, not minutes as many DBAs like to think. Werner Vogels wrote an excellent article about what eventual consistency and database durability mean: http://www.allthingsdistributed.com/2007/12/eventually_consistent.html

    Jeremiah Peschka
    Microsoft SQL Server MVP
    Managing Director - Brent Ozar PLF, LLC

  • Evil Kraig F

    SSC Guru

    Points: 100851

    A very handy article, Jeremiah, especially the revised one. Thanks for pointing it out. Much reading to be done!


    - Craig Farrell

    Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

    For better assistance in answering your questions[/url] | Forum Netiquette
    For index/tuning help, follow these directions.[/url] |Tally Tables[/url]

    Twitter: @AnyWayDBA

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply