whichdb

Tesora

discontinued

by Tesora, Inc. (formerly ParElastic) · since 2012 · also known as Tesora Database Virtualization Engine, Tesora DVE, ParElastic, Tesora DBaaS Platform

MySQL-protocol sharding layer (ex-ParElastic) and OpenStack Trove DBaaS vendor; bought by Stratoscale in 2017.

relationaldatabase engineopen source (copyleft)legacy
Website Source★ 16 Compare Find similar

discontinued. Acquired by Stratoscale in February 2017; the DVE repo has been idle since 2015 and Tesora products are no longer offered. Use Vitess, TiDB or PlanetScale.

Overview

Tesora started in 2010 as ParElastic, whose Database Virtualization Engine (DVE) sat between applications and a pool of MySQL or MariaDB servers, exposing one virtual MySQL-protocol database while transparently sharding data across storage nodes with ACID transactions across them. Renamed Tesora, the company open-sourced DVE under the AGPL in 2014 and shifted to an enterprise distribution of OpenStack Trove, the OpenStack database-as-a-service, becoming its leading contributor. Stratoscale acquired Tesora in February 2017 to build AWS-style database services, and both DVE and the Tesora DBaaS platform stopped as standalone products. For transparent MySQL sharding today, look at Vitess or a distributed SQL database.

Transactional apps (OLTP)

Strengths & trade-offs

Strengths

  • +Applications saw one MySQL database while data was sharded underneath
  • +Cross-shard ACID transactions without application changes
  • +Ran on standard MySQL or MariaDB servers

Trade-offs

  • −Discontinued after the 2017 acquisition; code idle since 2015
  • −Extra proxy hop and query-routing overhead
  • −AGPL community edition with a tiny user base

Great for

  • +Historical reference for MySQL sharding middleware
  • +Background on OpenStack Trove DBaaS

Think twice for

  • −Any new deployment

Capabilities

Native or official first-party support · 4 of 25 tracked

✓Transactions
✓Joins
✓Secondary indexes
✓Durable persistence
–Full-text search
–Vector search
–Geospatial
–JSON
–Change data capture
–Triggers
–Stored procedures
–Materialized views
–TTL / expiry
–Pub/Sub
–Columnar storage
–In-memory
–Compression
–Encryption at rest
–Role-based access
–Time travel
–Branching
–Online schema changes
–Streaming ingest
–Offline sync
–Runs in WebAssembly

Scale & consistency

Comfortable data size
Medium · ≤ 10 TB
Horizontal scaling
Native
Multi-region
No
Transactions
Full ACID
Consistency
Strong
Schema
Strict
Architecture
Distributed, Client server
Query languages
SQL

Scale-out by adding MySQL storage nodes behind the virtualization engine.

Deployment

Self-hosted Vendor-managed cloud Serverless Embedded Edge Kubernetes operator

Ecosystem

compatible withMySQL
apis & protocolsMySQL wire protocol

Alternatives to Tesora

Compare all→
VitessRelational21.2

CNCF-graduated sharding and clustering layer that makes a fleet of MySQL servers look like one database.

tesora vs vitess →
TiDBRelational35.9

MySQL-compatible distributed SQL with a row store for OLTP and a columnar replica for real-time analytics.

tesora vs tidb →
PlanetScaleRelational25.7

Performance-focused managed MySQL (Vitess) and Postgres, with NVMe-backed Metal clusters and branching.

tesora vs planetscale →
MySQLRelational82.3

The web's default open-source SQL database, now on calendar versioning with 9.7 as the LTS line.

tesora vs mysql →
MariaDBRelational56.2

Community-led MySQL fork with extra storage engines, built-in Galera and a faster feature cadence.

tesora vs mariadb →
Progress OpenEdgeRelational20.4

Integrated RDBMS plus ABL 4GL application platform behind thousands of ERP and vertical business apps.

tesora vs progress-openedge →

Tesora FAQ

What is Tesora?

Tesora is a relational database by Tesora, Inc. (formerly ParElastic), first released in 2012. Tesora started in 2010 as ParElastic, whose Database Virtualization Engine (DVE) sat between applications and a pool of MySQL or MariaDB servers, exposing one virtual MySQL-protocol database while transparently sharding data across storage nodes with ACID transactions across them. Renamed Tesora, the company open-sourced DVE under the AGPL in 2014 and shifted to an enterprise distribution of OpenStack Trove, the OpenStack database-as-a-service, becoming its leading contributor. Stratoscale acquired Tesora in February 2017 to build AWS-style database services, and both DVE and the Tesora DBaaS platform stopped as standalone products. For transparent MySQL sharding today, look at Vitess or a distributed SQL database.

Is Tesora open source?

Yes. Tesora is open source. License: GNU AGPL v3 (DVE community edition).

Does Tesora support ACID transactions?

Yes. Tesora supports full ACID transactions, with strong consistency.

Does Tesora scale horizontally?

Tesora scales horizontally out of the box, with built-in sharding or partitioning. It is comfortable at medium scale (≤ 10 TB).

How can I run Tesora?

You can self-host it.

What is Tesora best for?

Tesora is a strong fit for historical reference for MySQL sharding middleware and background on OpenStack Trove DBaaS. Think twice for any new deployment.

What are the best alternatives to Tesora?

Common alternatives to Tesora include Vitess, TiDB, PlanetScale, MySQL and MariaDB. The right choice depends on your workload, scale and hosting; WhichDB's smart match ranks them against your requirements.

Is Tesora still maintained?

Tesora is discontinued. Acquired by Stratoscale in February 2017; the DVE repo has been idle since 2015 and Tesora products are no longer offered. Use Vitess, TiDB or PlanetScale.

How popular is Tesora?

Tesora ranks #671 of 844 databases on the WhichDB Score (0.2/100), and #202 among relational databases. The score combines public adoption signals such as package downloads, GitHub activity, job posts and developer discussion.