Sign in / up

back to article What do you need to deliver next-gen Enterprise applications?

How relevant is NoSQL in the Enterprise? Join us live on 17 December at 11:00 GMT to find out. Once upon a time, there was only one mainstream database architecture. Relational databases management systems (RDBMS), which stored information in tables and enabled access via a structured query language, were the only real show in …

COMMENTS

House rules Send corrections
This topic is closed for new posts.
  1. Ilsa Loving

    NoSQL is great!

    When you don't care about transactional integrity (or really, integrity in general), or being able to reliably query the data in a standardized and deterministic way.

    1 2
    1. TerryDhariwal
      Reply Icon

      Re: NoSQL is great!

      Transactions are great for many use cases.

      But if you need high performance at scale - then you may need to sacrifice transactions. Real life is about tradeoffs, so I invite you to ponder on the reasons why Google and Facebook moved away from traditional RDBMSs and built their own NoSQL databases to satisfy their performance+scale needs.

      PS - Mutations in Couchbase are ACID per document. We are currently exploring ways of introducing transactions across multiple documents. However if we every add this functionality it will be optional - giving end-users the choice to tune the database for their needs.

      PS - I personally worked with Ian on this use-case and performance was a key reason why SKY moved away from their RDBMS

      0 0
      1. whiz
        Reply Icon

        Re: NoSQL is great!

        Google and Facebook both use MySQL which is an RDBMS

        0 0
  2. Richard Plinston

    > Once upon a time, there was only one mainstream database architecture.

    Once upon a time, the mainstream were using hierarchical database systems, then network (CODASYL) database systems (eg IDMS). There were also 'inverted file system' databases such as Adabas (original).

    While SQL became the mainstream database language, the underlying 'architecture' of different database systems is quite varied.

    4 0
    1. Where not exists
      Reply Icon

      Still hierarchical after all these years

      IMS...

      1 0
    2. TerryDhariwal
      Reply Icon

      The nice thing about Couchbase is that it gives you a distributed (networked) hierarchical database - but using commodity servers, it doesn't cost the earth (MIPS) and it also gives you SQL :-)

      0 0
  3. Joerg

    NoSQL is just a new facade driven by marketeers in the industry that doesn't make things anything easier nor better than SQL.

    0 1
    1. TerryDhariwal
      Reply Icon

      I have to strongly disagree with your comment (and yes I work for Couchbase)

      Firstly, its not about SQL vs NoSQL. Its actually Relational VS non-Relational. Also, its not even a competition - its actually about picking the right tool for the right job.

      RDBMSs make sense for some use-cases but aren't a good fit when you require web-scale and web-performance.

      Amadeus for example use Couchbase for mission critical and revenue impacting applications. They consciously chose Couchbase OVER Relational for particular use-cases because they needed to support millions of reads and writes per second at sub-millisecond response times.

      Remember, there is no right or wrong answer - only tradeoffs and making a choice between database systems that satisfy your needs (or most of them). Sometimes you may need to combine NoSQL with a RDBMS.

      PS - NoSQL echo's many traditional database systems before RDBMSs became mainstream.

      PS: Couchbase supports ANSI compliant SQL

      0 0
  4. Captain Server Pants

    Who needs reporting anyway!

    You can slap it up faster with a key value store.

    0 0
This topic is closed for new posts.

Other stories you might like