← Back to all sparks
A

Apache Seata

DEVOPS
Velocity2.5

Distributed transaction solution for microservices

Seata's first Apache release is stuck in a voting round, two years after its last shipped version.

distributed-transactionsapache-incubatorrelease-candidatesdatabase-supportgovernance
Current state
The feed shows a two-year gap between three legacy releases explicitly labelled 'Not Apache release' and a 2.7.0 release candidate cut for incubator voting in August 2026. The candidate is a second round: the first was cancelled over NOTICE copyright and organisation issues, and the rebuild came from a fixed commit. Its note is careful to say the artefacts are not an Apache release until votes pass and are promoted. The pre-donation releases had added SQL Server AT mode support, Dameng and PolarDB-X databases, IPv6, and a restructured TCC integration layer.
Where it's heading
Development has moved from feature work to the mechanics of donation. The visible energy is in NOTICE files, staging repositories and vote rounds rather than transaction semantics, which is the normal shape of an incubating project but leaves adopters on releases the project itself now disclaims. Nothing since 2024 has been generally available under either name.
Prediction
The path from here is a vote outcome rather than a feature; the entries do not indicate whether round two passed.

Recent moves

  1. 7d ago

    Second voting round for the first Apache release candidate

    The first movement in two years, and it is procedural: round one was cancelled over NOTICE copyright and organisation problems, and this rebuilds from the corrected commit for incubator voting. The note explicitly warns against treating the artefacts as a release.

    View source ↗
  2. 1y ago

    Rollback and XA transaction fixes on the pre-donation line

    A patch release addressing rollback failures from primary key case mismatches, XA transaction start exceptions and integer overflow in the table metadata cache. Labelled by the project as not an Apache release.

    View source ↗
  3. 1y ago

    Dameng and PolarDB-X 2.0 database support

    Two database engines added to AT mode, both aimed at the Chinese enterprise market where Seata has its deepest adoption. The rest is dependency and licensing cleanup that reads in hindsight as preparation for donation.

    View source ↗
  4. 1y ago

    TCC moved to an integration layer; SQL Server and IPv6 support

    The last major version before donation. Extracting a transaction-process integration layer made TCC accessible through an API rather than framework-specific hooks, and SQL Server AT mode plus IPv6 broadened where Seata could be deployed.

    View source ↗