Choosing datastores

Choosing datastores

Guide on how to select datastores to solve different problems

Make a submission

Submissions are closed for this project

How do you select datastores and be aware of their limitations when applied to the problem at hand? Are there misconceptions you wish someone had cleared for you as you started on your journey of scaling with datastores?

Choosing data stores for your use cases conference will help you understand:

  • Running datastores at scale - and tuning, debugging and operations.
  • Solving specific use cases with a certain datastore.
  • Data modelling and developer experience with datastore.

Senior infrastructure and software engineers from Farfetch, Aerospike, Zeotap,, LinkedIn and Tesco engineering will share war stories and their learnings with practitioners in the audience.

View schedule at

Contact information: Join the Rootconf Telegram group at or follow @rootconf on Twitter.
For inquiries, contact Rootconf at or call 7676332020.

Hosted by

Rootconf is a forum for discussions about DevOps, infrastructure management, IT operations, systems engineering, SRE and security (from infrastructure defence perspective). more

Apoorv Purohit

Managed MySQL Experience At LinkedIn

Submitted Aug 13, 2021

MySQL is used as a primary data store by a majority of internal tools at LinkedIn. We host over 2000 databases of different use-cases. To support our clients better, we have developed a few tools around MySQL. In this talk we will discuss how our tools improved the developer experience while using MySQL.
We will talk about how a database is requested and provisioned by the clients and how they get access to their respective databases the way they want i.e. from having an all-round admin access for complete control to only read-only access for Select queries. We will also throw some light on the Query Analyzer tool that has helped developers identify and fix their slow queries. Lastly, a brief about how the MySQL servers are highly available for the developers, which is achieved by the MySQL Orchestrator . With these tools in action, we provide the developers a managed MySQL experience at LinkedIn.

Key Points

  • How these tools make life of developers easy when they deal with MySQL
  • How access for MySQL are managed efficiently
  • How QAN adds value
  • How the applications feel negligible glitch when a primary host goes down and is failed over to a replica by orchestrator

Audience Takeaways

  • How we created a Managed MySQL Experience at LinkedIn
  • QAN is open sourced

Session Outline

  • Introduction (1 min)
  • MySQL at LinkedIn (3 min)
    • Basic Infrastructure
    • Different types of use-cases we support
  • How a DB is provisioned on MySQL (3 min)
  • Access Management (6 min)
  • Query Analyzer (6 min)
  • HA powered by MySQL Orchestrator (5 min)
  • Workflow in Motion (3 min)
    • From provisioning to analysing queries
  • Conclusion + Q&A (3 min)


{{ gettext('Login to leave a comment') }}

{{ gettext('Post a comment…') }}
{{ gettext('New comment') }}
{{ formTitle }}

{{ errorMsg }}

{{ gettext('No comments posted yet') }}

Chinmay Naik

Chinmay Naik

Using GitHub gh-ost to run Zero downtime online schema migrations in MySQL

What the talk is about Did you ever have to run an alter table on a production MySQL table containing 100M+ rows? If yes, then you have experienced the problem. MySQL Online schema migration for tables with millions of rows is hard. more

31 Jul 2021