TBase

TBase is a self-hosted distributed database for teams building transactional and analytical services in one cluster. It is best suited to operators comfortable compiling and managing database infrastructure; its flexible table layouts come with constraints that matter at schema design time.

Overview

TBase combines distributed database and warehouse services in a single cluster. Coordinators plan queries, DataNodes hold user data, and a Global Transaction Manager is part of the cluster architecture. The system can distribute tables or replicate them, then route queries to DataNodes and gather the results.

Its extended SQL subset includes transactions, foreign keys, user-defined types and functions. PostgreSQL-like language interfaces provide a familiar path for teams already using that ecosystem, but do not imply complete PostgreSQL compatibility.

Key features

Administrators can choose shard tables, partitioned shard tables, hot and cold partitioned shard tables, or replication tables. This gives teams options for organizing data, but shard-table distribution keys require commitment: their value, length and type cannot be changed. Replication tables keep a complete copy on every DataNode, making them unsuitable for large tables and limiting update performance.

TBase also provides security and audit functions. Its monitoring capabilities include session memory, execution details for DataNode operators, and cluster-wide active sessions viewed from a coordinator. These tools can help administrators inspect resource use and query activity across the cluster.

The pgxc_ctl tool helps configure and manage clusters, but does not remove the need to operate the underlying deployment.

Pricing

TBase is open source under the BSD 3-Clause License, with a listed third-party component exception. The TBase plan costs nothing. There are no paid tiers or seat, quota, or trial terms given for this plan.

Platforms

TBase is self-hosted, with platform support listed for Linux, macOS, Windows, Android and iOS. The deployment guide describes multi-host cluster deployment; teams should weigh that operational model against the breadth of platform labels when deciding where to run production infrastructure.

Who it's for

TBase fits teams that need horizontal scaling and HTAP workloads, and have the skills to compile and administer a self-hosted database. Its language interfaces similar to PostgreSQL, SQL capabilities and monitoring functions will appeal to teams seeking distributed data services without separating transactional and warehouse workloads. Teams with frequently changing shard keys, large replicated tables, or little appetite for infrastructure operations should look elsewhere.

For game development, TBase lists automated test execution, hybrid test environments, Unity and UE4 support, Android and iOS targets, and SDKs in C++, Java, Kotlin, Swift and Objective-C. It does not support playtesting workflows, so it is not a complete fit for teams whose testing needs center on playtesting.

Pros and cons

• Pros: Distributed database and warehouse services share one cluster, with horizontal scaling and HTAP workloads supported.
• Pros: Multiple shard and partition layouts, SQL transactions and foreign keys offer useful choices for data modeling.
• Pros: Session, operator and cluster-wide activity monitoring provides several views into workload behavior.
• Cons: Shard distribution-key value, length and type cannot be changed, making early schema decisions consequential.
• Cons: Replication tables duplicate full data on each DataNode and have low update performance, ruling them out for large or update-heavy tables.
• Cons: Source compilation and cluster deployment put operational responsibility on the adopting team.
• Cons: Playtesting workflows are unsupported despite the listed game testing capabilities.

Alternatives

Distributed SQL Databases is a broader category to browse when comparing distributed database options. Consider CrateDB if a free hosted tier with defined resources—2 vCPUs, 2 GiB RAM and 8 GiB storage—better suits the deployment; its Shared plan has custom pricing.

MySQL is another free-plan option, with a Community Edition described for SQL and NoSQL applications and replication and high-availability components. Choose OceanBase Database if you want a free community edition with full kernel capabilities.

VoltDB offers a free Developer Edition for individual developers and early exploration, including local or cloud use, sample apps, tutorials and documentation. CockroachDB Cloud is a cloud alternative with a free plan and usage billed monthly by the minute; its Standard rate starts at $0.06 a month for AWS us-east-1 and varies by region.

PrestoDB is a free, self-hosted SQL query engine rather than the distributed database-and-warehouse cluster TBase provides. TiDB Cloud is worth considering for a hosted option: its free Starter plan includes 25 GiB row storage, 25 GiB column storage and 250M requests, with free quotas applying per organization. YugabyteDB Anywhere may suit teams evaluating a paid platform; its evaluation license lasts up to 32 consecutive calendar days, while production requires a commercial license.

For more focused comparisons, browse Game Testing Software or Mobile Databases.

Verdict

Choose TBase if your team can run a self-hosted cluster and wants distributed transactional and analytical services, SQL capabilities and operational monitoring in one system. The open-source price is compelling, but the fixed shard-key properties and the cost of deployment and administration make it a poor fit for teams that need schema flexibility or managed operations.