Aranguent Laravel Package

Product Decisions This Supports

• Database backend selection: Informs whether to adopt ArangoDB as the primary data store for a Laravel application, especially when multi-model (document, graph, key-value) capabilities are required.
• Build vs. buy for database integration: Provides a ready-made Laravel-native integration layer, reducing the need to build and maintain custom ArangoDB connectors, query builders, and Artisan tooling.
• Feature roadmap prioritization: Enables planning for features that depend on advanced query and schema operations—e.g., whereLike, lateralJoin, union aggregates, array operators, multidimensional indexes, and graph/analyzer schema management.
• Upgrade and platform strategy: Signals a hard dependency on Laravel 12 and PHP 8.4; helps decide when to schedule framework/runtime upgrades and how to sequence them with product releases.
• Risk management for beta dependencies: Highlights that the package is still in beta with breaking changes, informing decisions about production readiness, version pinning, and contingency plans.
• Developer experience and operational tooling: Supports decisions to standardize on Artisan commands (db:table, db:show, model:show) for debugging and operational visibility.

When to Consider This Package

• Consider adoption when:
  • Your product genuinely needs ArangoDB’s multi-model capabilities (graph traversals, document storage, key-value) and you want to stay within Laravel conventions.
  • Your team is on—or ready to move to—Laravel 12 and PHP 8.4.
  • You need advanced query-builder features such as whereLike, lateralJoin, insertOrIgnoreUsing, union aggregates, and ArangoDB-specific array operators.
  • You want schema-builder parity with Laravel (views, analyzers, graphs, indexes, multidimensional indexes) and Artisan support for inspection.
  • You can tolerate beta-level stability, pin versions, and absorb breaking changes through planned upgrade cycles.
• Look elsewhere when:
  • You require production-grade stability and long-term support commitments; this is still a 1.0.0-beta.x release.
  • Your application must remain on Laravel 11 or earlier—this release explicitly drops Laravel 11 support.
  • Your use case is simple relational CRUD and does not benefit from ArangoDB’s multi-model features.
  • Your team lacks ArangoDB operational expertise and cannot invest in testing, monitoring, and upgrade coordination.
  • You need a mature ecosystem with broad community support and minimal breaking-change risk.

How to Pitch It (Stakeholders)

• To executives: This package unlocks ArangoDB’s graph and document capabilities inside Laravel without building a custom integration from scratch. It can accelerate delivery for features that depend on multi-model data, but it is still beta and carries upgrade risk. Recommend a time-boxed pilot or internal prototype, with a clear go/no-go gate before committing production workloads.
• To engineering: The release brings meaningful Laravel alignment—improved query builder operators, schema builder parity, Artisan commands (db:table, db:show, model:show), and PHP 8.4/Laravel 12 support. However, it includes breaking changes (Laravel 11 removed; getAllViews/getAllAnalyzers/getAllGraphs renamed), so plan a coordinated upgrade, pin the beta version, and add regression tests around schema inspection and query behavior. Treat it as a strategic dependency with active version management, not a drop-in commodity.