Hypervel Influxdb Laravel Package

Product Decisions This Supports

• Observability and time-series roadmap: Supports decisions to add InfluxDB-backed metrics, events, or telemetry in Hypervel/Laravel-style PHP services using InfluxQL, especially where the team wants a maintained package rather than a custom client.
• Build vs. buy: v0.2.0 strengthens the case for adopting rather than building: real InfluxDB integration tests, a named FailureStore, Packagist install documentation, and PHPStan level 6 reduce bespoke integration and reliability work.
• Upgrade and release planning: The breaking change to keep the “twin InfluxQL stacks” in step is a release gate. Plan regression testing for writes, queries, dashboards, and any assumptions about which InfluxQL stack is active.
• Platform standardization: The package requires hypervel/components 0.4.x-dev, which also sets the PHP version. Adopt only if the platform is already on that line or the team accepts dev-branch dependency risk.
• Production risk acceptance: Pre-1.0 status plus a 0.4.x-dev dependency means this is better suited to internal telemetry, pilots, or buffered/retryable workloads than low-risk critical paths.

When to Consider This Package

• Consider it when a Hypervel application needs InfluxDB/InfluxQL integration and the team values integration tests, failure handling, static analysis, and documented Packagist installation.
• Consider it for internal observability, metrics pipelines, event telemetry, or workloads where failed writes can be stored, retried, or tolerated.
• Validate before adoption: FailureStore semantics, supported InfluxDB versions, query coverage, upgrade path for the twin InfluxQL stacks, and compatibility with hypervel/components 0.4.x-dev.
• Look elsewhere if the product is on stable-only dependencies, uses Laravel rather than Hypervel, requires an official first-party InfluxDB client, needs 1.0/API stability, or cannot run real InfluxDB integration tests.
• Avoid using it as a core revenue-path dependency until the platform constraint moves off 0.4.x-dev and the breaking-change cadence settles.

How to Pitch It (Stakeholders)

Executives: This package provides a maintained InfluxDB integration for Hypervel-style PHP applications, with improved reliability signals in v0.2.0: real integration tests, failure handling via FailureStore, stronger static analysis, and clearer installation. It is still pre-1.0 and tied to a dev platform branch, so recommend a pilot for observability/telemetry rather than critical transactional workloads.

Engineering: v0.2.0 is a quality step—PHPStan level 6, real InfluxDB integration tests, FailureStore, and Packagist documentation—but it includes a breaking change in the InfluxQL stacks. Budget upgrade testing for queries, writes, and dashboards, and confirm hypervel/components 0.4.x-dev compatibility before committing. Treat it as a strategic fit only if Hypervel is already the platform.