Influxdb Odm Laravel Package

Product Decisions This Supports

• Platform modernization: v1.6.0 sets PHP 8.1 as the minimum and requires doctrine/persistence 3, making this a forcing function for upgrading runtime and persistence dependencies. PMs can use it to sequence PHP/runtime upgrades alongside feature work rather than as an isolated engineering chore.
• Dependency consolidation and risk reduction: Removing the doctrine/annotations requirement and decoupling AttributeDriver from AnnotationDriver reduces reliance on annotation parsing. This supports decisions to standardize on native PHP attributes and shrink the third-party surface area.
• Build vs. buy: If the product runs Doctrine ORM inside a Laravel codebase, this package provides a maintained mapping integration instead of custom metadata/attribute wiring. Adoption is justified where engineering would otherwise build and own Doctrine-to-Laravel mapping glue.
• Migration roadmap: Teams still using annotations need a defined migration path to attributes. This release is an enabler for that roadmap, but it also marks the point where legacy annotation support should be treated as technical debt.
• Use cases: Laravel applications using Doctrine ORM entities alongside Eloquent, especially those modernizing metadata mapping, consolidating persistence libraries, or preparing for PHP 8.1+ baselines.

When to Consider This Package

Consider adoption when:

• The application is on, or can move to, PHP 8.1+.
• The codebase uses or plans to use Doctrine ORM within Laravel and wants attribute-based entity mapping.
• The team is prepared to move to doctrine/persistence 3 and validate compatibility with existing Doctrine integrations.
• Reducing dependence on doctrine/annotations is a stated maintenance or security objective.
• The product roadmap includes framework/runtime modernization and this package can be upgraded as part of that work.

Look elsewhere or defer when:

• The platform is pinned below PHP 8.1, or cannot yet adopt doctrine/persistence 3.
• The codebase depends heavily on Doctrine annotations and has no near-term migration plan; v1.6.0 is a breaking upgrade in practice for that setup.
• The product uses Eloquent only and has no Doctrine ORM requirement.
• The team needs a drop-in upgrade with no dependency or migration effort; this release requires compatibility validation and likely code changes.

How to Pitch It (Stakeholders)

For executives: This is an infrastructure upgrade, not a user-facing feature. It reduces long-term dependency and maintenance risk by dropping the annotations requirement and aligning with supported PHP and Doctrine persistence versions. The trade-off is an engineering upgrade: the application must be on PHP 8.1+ and doctrine/persistence 3, and any annotation-based entity mappings will need migration to attributes. Recommend funding this as part of the platform modernization roadmap rather than as a standalone initiative.

For engineering: v1.6.0 is a compatibility-breaking release for older environments. Validate PHP 8.1+, doctrine/persistence 3, and all Doctrine integrations first. Inventory annotation usage and plan the move to attributes. The decoupling of AttributeDriver from AnnotationDriver is the right long-term direction, but it should be treated as a migration project with regression coverage, not a routine patch upgrade.