Fluentaql Laravel Package

Product Decisions This Supports

• Feature delivery for ArangoDB-backed Laravel apps: Use FluentAQL as a fluent PHP query-building layer for AQL instead of hand-writing raw AQL strings in application code. This supports features such as graph traversal views, document search, reporting queries, internal admin tooling, and data migration/backfill scripts.
• Build vs. buy/borrow: For a narrow, non-critical integration, this can be treated as a “borrow” decision: MIT-licensed OSS reduces initial build effort versus creating an in-house AQL builder. For a platform-level commitment, the archived status and near-zero adoption weaken the buy case and favor a maintained fork, official ArangoDB drivers, or a thin internal adapter.
• Roadmap gating: Do not place this package on a strategic roadmap unless ArangoDB is already a committed part of the architecture. If ArangoDB adoption is under evaluation, treat FluentAQL as an implementation detail, not a reason to choose ArangoDB.
• Legacy and maintenance decisions: The package is best positioned as a tactical dependency for existing Laravel/PHP systems with ArangoDB, or for low-risk prototypes. It is not a strong signal of ecosystem maturity: 12 stars, 0 dependents, last release in May 2022, and archived status mean the PM should budget for vendoring/forking and eventual replacement.
• Use cases to prioritize: Internal tools, one-off data operations, prototypes, reporting utilities, and bounded feature work where raw AQL is error-prone but full ORM capability is unnecessary. Avoid using it as the foundation for critical multi-tenant data access, complex transactional workflows, or long-lived public APIs without an explicit maintenance plan.

When to Consider This Package

Consider FluentAQL when:

• The product already runs ArangoDB and the application is Laravel/PHP-centric.
• The team needs a query-construction convenience layer for AQL, not a full ORM, schema manager, or migration framework.
• The scope is bounded and non-critical, such as internal dashboards, admin queries, reporting, or data cleanup scripts.
• Engineering can pin, vendor, or fork the package and accept ownership of bug fixes, compatibility work, and security review.
• The alternative is hand-rolled raw AQL throughout the codebase, and a small fluent builder would improve readability and parameter handling enough to justify the dependency.
• The team has a clear exit path to raw AQL, the official ArangoDB PHP driver, or an internal query abstraction.

Look elsewhere when:

• This is a new greenfield product with no existing ArangoDB commitment.
• The product requires active upstream maintenance, security patching, SLA-backed support, or predictable Laravel version compatibility.
• The workload involves complex AQL, graph algorithms, transactions, schema management, or high-scale data access patterns beyond simple query building.
• The organization has a policy against archived dependencies or requires healthy ecosystem validation; 12 stars and 0 dependents are weak adoption signals.
• A maintained official driver or a thin internal HTTP/client wrapper would meet the need with less long-term ownership risk.

How to Pitch It (Stakeholders)

For executives: FluentAQL is a small MIT-licensed Laravel package that can reduce implementation effort for ArangoDB query code in narrow, low-risk scenarios. It is not a strategic platform bet: the project is archived, has minimal adoption, and has not been released since 2022. Approve it only as a tactical dependency with capped exposure, a named internal owner, and a replacement plan. Do not let it become a reason to adopt ArangoDB or a hidden dependency in critical paths.

For engineering: FluentAQL offers a fluent PHP interface for building AQL queries, which can remove repetitive raw-string query construction in Laravel services. Treat adoption as a fork-or-vendor decision: pin the version, add integration tests around generated AQL, document supported query patterns, and avoid spreading its API across the domain layer. Prefer wrapping it behind a repository/query interface so the team can swap to raw AQL or the official ArangoDB driver later. The main risk is not license cost; it is maintenance ownership after archival and low ecosystem validation.