Rootconf 2019

On infrastructure security, DevOps and distributed systems.

Participate

OLTP or OLAP? Why not both?

Submitted by Jiten Vaidya (@jvaidya) on Monday, 6 May 2019

videocam_off
Section: Full talk Technical level: Intermediate Session type: Demo

Vote on this proposal

Login to vote

Total votes:  +1

Abstract

vitess.io is an open source sharding middleware system that runs massive OLTP workloads at companies susch as Youtube, Slack and Square. Vitess recently added support for cross-shard materialized views and near real-time rollups - traditionally considered to be OLAP features. The underlying feature that enables this is “VReplication” - the ability to parse MySQL binary log and use it to enable interesting use-cases. I will explain the architecture of Vitess, the genesis of Vreplication for resharding databases and demonstrate VReplication in action for cross-shard materialized views and roll-ups.

Outline

  • Vitess history
  • Vitess architecture
  • Vitess resharding and demo
  • VReplication explained
  • VReplication demo

Requirements

Laptop with an internet connection.

Speaker bio

Jiten Vaidya is the co-founder and CEO at PlanetScale. Prior to starting PlanetScale, Jiten held various backend and infrastructure roles at US Digital Service, Dropbox, Youtube and Google. At Youtube, he managed the teams that operated Youtube’s MySQL databases at massive scale using the open source software, vitess.io.

Comments

  • 1
    Zainab Bawa (@zainabbawa) Reviewer 10 days ago

    Thanks for the submission, Jiten.

    Here are the initial comments for structuring the presentation:

    1. In the history of Vitess, you will have to lay out the problem that Vitess solves.
    2. What are the other solutions in the market, and how do they compare with Vitess. A visual or a table will be helpful.
    3. Since this is a talk, the goal is to give participants enough information to get them excited to try Vitess. Therefore, you have to share use cases and real-life examples (in some detail) where Vitess was used, and before-after scenarios.
    4. What are the trade-offs of using Vitess?
    5. How do teams, which are using other methods and solutions, implement Vitess? What are the challenges of introducing Vitess later in the organization’s tech journey?

Login with Twitter or Google to leave a comment