Rockset, the real-time indexing database company, announced the integration of MySQL and PostgreSQL. These integrations will support developers to run sub-second, high-concurrency analytics on data from MySQL and PostgreSQL.

These integrations will allow developers to rely on their relational database for online transaction processing (OLTP); meanwhile, Rockset will power real-time analytics at cloud scale. The outcome will be reduced load on the primary OLTP database; the reason is Rockset is able to handle the analytical queries, which would otherwise bring significant cost and risk to the primary database.

“MySQL and PostgreSQL are among the most popular databases in the world, however developers still find them impossible to scale as the volume of data grows. They either are forced to vertically scale existing databases by adding more compute resources, or give up on them completely in favor of a more horizontally scalable option,” said Venkat Venkataramani, Co-founder and CEO at Rockset. “These alternatives are painful and no longer acceptable in our cloud-first world, one where scale and speed are of utmost importance. Our new integration for MySQL and PostgreSQL is yet another example of Rockset removing the many barriers developers face when building modern data applications.”

Since the world is moving toward real-time analytics, applications running programmatic queries, traditional warehouses are reducing in number. With the impact of Rockset, developers using MySQL and PostgreSQL can:

  • Achieve better database performance by isolating analytical queries on Rockset, which ultimately scales horizontally in the cloud.
  • Run sub-second analytical queries, including JOINS with other databases, event streams, and lakes.
  • Deliver real-time reporting by using one of Rockset’s integration with visualization tools such as Retool, Superset, Redash, or Tableau.

The support for MySQL and PostgreSQL is now live. So now, the potential clients can expect that Rockset will next train its sights to more of the usual suspects in enterprise databases.