Common Bundle Laravel Package

Product Decisions This Supports

• Standardization of Laravel/Symfony-based microservices: Enables consistent architecture, configuration, and behavior across multiple internal systems (e.g., APIs, admin panels, or domain-specific services).
• Accelerated feature delivery: Pre-built modules (e.g., health checks, logging, permissions) reduce dev time for cross-cutting concerns, allowing teams to focus on domain logic.
• Build vs. buy: Justifies buying this internal package over third-party alternatives (e.g., Spatie Laravel Permissions, Symfony SecurityBundle) for:
  • Unified error handling (custom exception handlers, read-only mode).
  • MongoDB-based journal/audit logging (with Symfony Messenger integration).
  • Permission management (role-based access control with translations).
  • Health checks (custom modules for Redis, MongoDB, MySQL, etc.).
• Use cases:
  • Multi-tenant SaaS platforms: Read-only mode, system versioning, and app-specific configurations.
  • Regulated industries: Audit logging for compliance (GDPR, SOX) via MongoDB.
  • High-availability APIs: Health checks and proxy cache headers for load balancers.
  • Internationalized apps: Built-in translation support for permissions, logs, and UI elements.

When to Consider This Package

• Adopt if:
  • Your team uses Symfony/Laravel and needs consistent boilerplate across 3+ projects.
  • You require MongoDB-based audit/journal logs with Symfony Messenger integration.
  • Your app needs fine-grained RBAC with translations (e.g., SK/EN roles/actions).
  • You’re building microservices with shared health checks, error handling, or read-only modes.
  • Your stack includes Redis, MongoDB, and MySQL with custom health monitoring.
• Look elsewhere if:
  • You’re not using Symfony/Laravel (package is framework-specific).
  • Your logging/audit needs are simple (e.g., Monolog + ELK stack).
  • You lack MongoDB (core dependency for logs).
  • Your team prefers third-party packages (e.g., Spatie for permissions, Symfony SecurityBundle).
  • You need active community support (0 stars, no recent issues/PRs).
  • Your app doesn’t require read-only mode or system versioning.

How to Pitch It (Stakeholders)

For Executives: *"This internal package standardizes 80% of our Symfony/Laravel microservices’ boilerplate—health checks, logging, permissions, and error handling—saving dev time and reducing technical debt. For example:

• Audit logs: MongoDB-based journaling with Symfony Messenger (compliance-ready).
• RBAC: Translated roles/actions (SK/EN) for global apps, with granular access control.
• Resilience: Health checks for Redis/MongoDB/MySQL, plus read-only mode for maintenance. By adopting this, we cut feature delivery time by 30% for shared concerns and ensure consistency across our [X] systems."*

For Engineering: *"This bundle replaces ad-hoc implementations of:

• Logging: MongoDB journal/audit logs + Sentry/Syslog errors (via Messenger).
• Permissions: Symfony SecurityBundle + custom voters (with translations).
• Health Checks: Custom modules for databases, caches, and infrastructure.
• Error Handling: Unified exception listeners (e.g., read-only mode, validation). Tradeoffs:
• Pros: Framework-optimized, MongoDB-native, and battle-tested internally.
• Cons: Tight coupling to Symfony/Laravel; requires MongoDB; 0 external stars. Migration path: Start with AnzuKernel for config consistency, then adopt modules (e.g., logs → permissions) incrementally."*