Clarc Bundle Laravel Package

Product Decisions This Supports

• RBAC & Security: Accelerates implementation of role-based access control (RBAC) with pre-built AuthorizationChecker and permission endpoints, reducing dev time for permission-heavy applications (e.g., SaaS platforms, admin dashboards).
• Microservices Communication: Enables asynchronous messaging between services via AMQP (RabbitMQ) with Protobuf serialization, ideal for event-driven architectures (e.g., order processing, notifications). Avoids reinventing message buses from scratch.
• Dynamic Navigation: Simplifies permission-aware UI navigation (e.g., admin panels) by auto-generating menus based on user roles, cutting frontend-backend sync overhead.
• API Standardization: Provides consistent API responses (via NullObjectArraySerializer) and domain exceptions (DomainHttpException), ensuring uniformity across microservices or monoliths.
• Build vs. Buy: Buy for teams needing RBAC, messaging, or navigation out-of-the-box. Build only if requiring custom security logic or non-AMQP messaging.
• Roadmap Priorities:
  • Phase 1: Integrate RBAC for user permissions (low risk, high ROI).
  • Phase 2: Adopt messaging for cross-service communication (medium risk, scalable).
  • Phase 3: Implement dynamic navigation (UI/UX improvement).

When to Consider This Package

• Adopt if:
  • Your Symfony/PHP app requires RBAC (e.g., admin panels, multi-tenant SaaS).
  • You need asynchronous messaging between services (e.g., event sourcing, workflows) and can use AMQP/RabbitMQ.
  • You want dynamic, permission-gated navigation without manual route/permission mapping.
  • Your team lacks expertise in Symfony Messenger or Protobuf but needs production-ready messaging.
• Look elsewhere if:
  • You’re not using Symfony 6+ or PHP 8+ (package is tightly coupled).
  • Your security model is attribute-based (ABAC) rather than role-based (RBAC).
  • You need non-AMQP messaging (e.g., Kafka, Redis Streams).
  • Your project is small-scale (overhead may not justify benefits).
  • You require real-time updates (WebSockets) instead of async messaging.

How to Pitch It (Stakeholders)

For Executives: *"This package cuts 3–6 months of dev time by providing battle-tested RBAC, async messaging, and dynamic navigation for Symfony apps. For example:

• RBAC: Replace custom permission logic with a pre-built /user/permissions API and AuthorizationChecker, reducing security bugs.
• Messaging: Enable scalable event-driven workflows (e.g., order processing) without building a message broker from scratch.
• Navigation: Auto-generate role-based menus (e.g., admin dashboards) in hours, not weeks. ROI: Justify as a foundation for future microservices or compliance-heavy apps (e.g., healthcare, finance). Low risk—MIT license, active maintenance."*

For Engineering: *"Clarc Bundle gives us:

1. RBAC: Plug-and-play AuthorizationChecker and permission endpoints. Example:

   # config/packages/artox_lab_clarc.yaml
   artox_lab_clarc:
       security:
           rbac:
               permissions:
                   ROLE_MAINTAINER: [show, edit]
   

   Check permissions in controllers:

   $this->authorizationChecker->isGranted('edit'); // true/false
   

2. Async Messaging: Protobuf + AMQP for cross-service communication. No more reinventing wheels:

   $this->bus->dispatch(new OrderCreated($orderId)); // Sent to RabbitMQ
   

   Consume with:

   php bin/console messenger:consume listening
   

3. Dynamic Navigation: Define menus in YAML, auto-filter by permissions:

   left_menu:
       items:
           - title: Companies
             link: /companies
             permissions: company.list
   

   API: /user/navigations returns only accessible items. Trade-offs:

• Lock-in: Tied to Symfony 6+/PHP 8+.
• Learning curve: Protobuf/AMQP if new to the team. Recommendation: Start with RBAC (low risk), then expand to messaging/navigation as needed."*