Laravel Tidb Laravel Package

Product Decisions This Supports

• Platform currency / upgrade planning: v5.0.0 adds Laravel 12 support, so this directly feeds the roadmap question "when can we move our TiDB-backed services onto Laravel 12?" It unblocks or de-risks a framework upgrade for any product surface running on TiDB.
• Build vs buy on database glue: TiDB is MySQL-wire-compatible but has behavioral differences (distributed transactions, auto-increment handling, JSON/index semantics). This package encapsulates those Laravel-side adjustments. Adoption is a "buy/borrow" decision that avoids your team owning bespoke connector code and migration macros.
• Feature feasibility on TiDB: Teams evaluating HTAP-style analytics alongside OLTP, horizontal scaling past single-node MySQL limits, or multi-region read patterns can treat Laravel + TiDB as a viable stack — this package is what makes that stack ergonomic for the default Laravel feature set (migrations, Eloquent, query builder, schema builder).
• Technical debt containment: Choosing a maintained connector with an explicit Laravel version matrix reduces the risk of frozen, forked DB drivers in your codebase when Laravel majors ship.
• Vendor/ecosystem signal: A v5.0.0 tagged release coinciding with Laravel 12 tells you the maintainer is tracking upstream Laravel cadence — a relevant input for renewal/keep-vs-replace reviews.

When to Consider This Package

Adopt when all of the following hold:

• You run (or are evaluating) TiDB as your primary datastore for a Laravel application, and you need the Laravel database layer — migrations, schema builder, Eloquent — to behave predictably against it.
• You are standardizing on Laravel 12 (or are on 11/12 and planning the jump). v5.0.0 is the release line that carries Laravel 12 compatibility; older majors should be assumed tied to older Laravel versions, so validate the version matrix before pinning.
• The alternative is owning custom driver/schema code — in that case this package is a clear net reduction in maintenance surface.
• You want a small, focused dependency rather than a heavyweight ORM-fork or a DBA-tooling suite.

Look elsewhere when:

• You are on MySQL, MariaDB, or PostgreSQL — this package is TiDB-specific and adds unnecessary surface.
• You need deep TiDB operational features (TiFlash placement rules, PD/Region tuning, TiCDC pipelines, backup/restore orchestration). This is a Laravel integration layer, not a TiDB operations toolkit; plan to solve those with TiUP/operator tooling.
• You require a large third-party ecosystem or commercial support SLA — this is a community package from a single organization; budget for the possibility of upstreaming your own fixes.
• You are locked to an older Laravel major and cannot upgrade — confirm whether v5.0.0 dropped support for your version before adopting, since the major-version bump is driven by framework compatibility.

How to Pitch It (Stakeholders)

To executives: We can now run our Laravel applications on TiDB with a supported, Laravel 12-compatible integration. That removes a blocker on our framework upgrade and keeps our database scaling options open (horizontal scale, HTAP reads) without asking engineering to build and maintain database driver code themselves. The cost is one small dependency; the saving is avoided bespoke connector work and a cleaner path through the Laravel 12 upgrade.

To engineering: v5.0.0 is a compatibility release — it adds Laravel 12 support and is the release line to target for the Laravel 12 migration. Practical implications:

• Treat the major bump as a version-compatibility boundary, not a feature change. Verify the supported Laravel/PHP matrix before upgrading, and confirm whether Laravel 11 and below remain supported on this line or require staying on v4.x.
• Budget a regression pass on migrations and schema builder after upgrading — schema-diff behavior against TiDB is the most likely place a framework-major shift surfaces issues.
• If we adopt, pin the version and track the repo's release cadence; the maintainer moving to v5.0.0 alongside Laravel 12 is a positive maintenance signal but does not replace our own upgrade testing.