Hierarchybundle Laravel Package

Product Decisions This Supports

• Organizational Data Modeling: Enables structured representation of company hierarchies (e.g., departments, teams, reporting lines) for internal tools, HR systems, or access control.
• Graph-Based Relationships: Justifies adoption of Neo4j for complex relational queries (e.g., "Find all employees under a manager’s manager") vs. traditional SQL.
• Admin vs. User Access: Supports tiered UIs (admin for hierarchy management, public for browsing) to reduce custom development for role-based interfaces.
• Build vs. Buy: Avoids reinventing hierarchy management wheels; leverages existing Neo4jPHP library for graph operations.
• Roadmap for Scalability: Future-proofs for dynamic org structures (e.g., mergers, promotions) without schema migrations.
• Compliance/Access Control: Integrates with Symfony security systems to map Neo4j roles (e.g., manager) to application permissions.

When to Consider This Package

• Avoid if:
  • Your hierarchy is flat or static (e.g., simple team lists without nested relationships).
  • You’re not using Neo4j (package requires Neo4jPHP; switching databases would need refactoring).
  • You need fine-grained customization (e.g., non-standard relationship types, multi-tenancy).
  • Your team lacks Symfony/Bundle experience (setup requires kernel registration, YAML config).
  • You prioritize performance at scale (Neo4jPHP may not match native drivers for high-throughput apps).
• Look elsewhere if:
  • You need multi-level inheritance (e.g., "group → subgroup → user" with custom rules).
  • Your hierarchy involves non-hierarchical relationships (e.g., cross-team collaborations).
  • You’re using Drupal, Laravel, or non-Symfony frameworks (bundle is Symfony-specific).

How to Pitch It (Stakeholders)

For Executives: "This bundle lets us model our org structure as a graph—like an interactive org chart—using Neo4j, which is faster for complex queries than SQL. It includes admin tools to update hierarchies (e.g., promotions, reorgs) and a public view for employees. We avoid building this from scratch, saving dev time while enabling features like role-based access control tied to the hierarchy. Low risk: it’s a thin wrapper around Neo4jPHP, and the admin UI reduces manual data entry errors."

For Engineering: *"HierarchyBundle gives us:

• Pre-built Neo4j integration for hierarchical data (groups/users with PART_OF/MEMBER_OF relationships).
• Symfony-friendly (configurable via YAML, routes included, admin UI).
• Minimal custom work: Just configure Neo4j credentials and root group ID. Tradeoffs: Tightly coupled to Neo4jPHP (not the official driver) and lacks docs/examples. We’d need to validate performance for our query patterns (e.g., depth-first traversals)."*