1. 11
  1.  

  2. 4

    Not to be a wet blanket, but I’m not sure why I should be excited about 120k writes/s on a 15 node SSD cluster.

    1. 1

      Running in a single datacenter or worse, on a single node, is not really viable in 2017. If you want scalable, globally consistent transactions there is nothing else to choose from. That’s why there’s a lot of excitement about distributed transaction protocols these days.

      1. 1

        Running in a single datacenter or worse, on a single node, is not really viable in 2017

        That’s a bit bold. Sometimes keeping things simple is worth more than keeping things globally available.

        1. 1

          There’s lots of organizations thst keep their main database in a cluster that’s strongly consistent due to physical proximity and often dedicated lines. VMS and NonStop clusters were often done this way. Such a setup can be replicated on a per country or per continent basis.

      2. 2

        We are super excited to be one of the first commercial users of the Calvin protocol http://cs.yale.edu/homes/thomson/publications/calvin-sigmod12.pdf

        1. 1

          Are you using the (automatic) reconnaissance txn approach or are you requiring that all txns declare their read/write set ahead of time?

          1. 1

            Reconnaissance.

            Unusual username you have there.