Upgrade to Pro — share decks privately, control downloads, hide ads and more …

NewSQL: what, when and how

NewSQL: what, when and how

The database has always been one of the key components in every architecture. There is a great variety of tradeoffs we should consider and implementation that we can pick from. If we need consistency and correctness in exchange of availability and performance, we should pick a relational database. If we need scale and increased availability by sacrificing transactional and consistency guarantees, we should use a NoSQL database. And if we need both horizontal scalability and transactions, we need to pick a NewSQL database. During this talk we’ll explore what guarantees a NewSQL system provides. We’ll go over the different approaches in building such a system. And we’ll see some open source projects that implements each approach. At the end of the talk we’ll have a good understanding of when and how to apply a NewSQL database in our big scale applications.

Nikolay Stoitsev

November 03, 2018
Tweet

More Decks by Nikolay Stoitsev

Other Decks in Programming

Transcript

  1. Cover Title Goes here Month XX, 20XX NewSQL: What, When

    and How Nikolay Stoitsev @ Uber Engineering Sofia
  2. F. Chang, J. Dean, S. Ghemawat, W. C. Hsieh, D.

    A. Wallach, M. Burrows, T. Chandra, A. Fikes, and R. E. Gruber. Bigtable: A distributed storage system for structured data. ACM Trans. Comput. Syst., 26:4:1–4:26, June 2008.
  3. G. DeCandia, D. Hastorun, M. Jampani, G. Kakulapati, A. Lakshman,

    A. Pilchin, S. Sivasubramanian, P. Vosshall, and W. Vogels. Dynamo: amazon’s highly available key-value store. SIGOPS Oper. Syst. Rev., 41:205–220, October 2007.
  4. RDBMS Easy to run it Has transactions Can scale Provides

    availability NoSQL NewSQL Can scale Has Transactions