Pmu Laravel Package

Product Decisions This Supports

• Modular Plugin Ecosystem: Enables plugin-based extensibility for sub-projects within a monorepo, allowing teams to add reusable functionality (e.g., logging, caching, or custom validation) without modifying core package logic. Aligns with domain-driven design (DDD) by isolating cross-cutting concerns into plugins.
• Accelerated Feature Rollouts: Supports incremental adoption of shared utilities/plugins across packages, reducing friction for teams migrating from multi-repo to monorepo. Plugins can be developed and tested in isolation before integration.
• Vendor/Partner Extensibility: Ideal for open-core models or third-party integrations, where plugins can encapsulate partner-specific logic (e.g., payment gateways, analytics) without polluting the main codebase.
• Roadmap for "Package Marketplaces": Justifies building an internal "Laravel package store" where teams can discover, install, and manage plugins for common use cases (e.g., @pmu/plugin-auth, @pmu/plugin-queue).
• CI/CD Pipeline Optimization: Plugins can be versioned and deployed independently, enabling canary releases or A/B testing of new features across sub-projects.

When to Consider This Package

• Adopt if:

  • Your team needs to standardize reusable plugins across Laravel/PHP packages (e.g., shared logging, caching, or validation layers).
  • You’re building a modular architecture where sub-projects require dynamic, composable features (e.g., microservices with optional modules).
  • You want to reduce boilerplate for cross-cutting concerns by leveraging community or internal plugins (e.g., @pmu/plugin-rate-limiting).
  • Your roadmap includes partner integrations or third-party extensions that should live outside the core codebase.
  • You’re using PMU for monorepo management and want to further optimize developer workflows with plugin-based tooling.

• Look elsewhere if:

  • Your use case doesn’t require plugin-based extensibility (e.g., you only need basic dependency management).
  • You’re constrained by legacy systems that can’t accommodate plugin architectures.
  • Your team lacks the bandwidth to curate or develop plugins, making the feature overhead unjustified.
  • You prioritize minimal tooling and plugins add unnecessary complexity for your current scale.

How to Pitch It (Stakeholders)

For Executives: "This update unlocks a game-changer for how we build and scale Laravel/PHP packages. With plugins for sub-projects, we can now treat shared utilities—like logging, caching, or auth—as first-class citizens that teams can install and customize without touching the core codebase. Imagine rolling out a new feature like rate-limiting across all our microservices with a single plugin install. This reduces technical debt, speeds up development, and even opens doors for monetizing internal tools as reusable plugins. The MIT license keeps costs zero, and the active development (last release: Dec 2025) ensures we’re future-proof. Let’s pilot this with our auth and payments packages to see how much faster we can iterate."

For Engineering: *"PMU’s plugin system solves two big problems:

1. No more copy-pasting shared logic: Need a new validation rule? Build it as a plugin and reuse it across packages.
2. Isolated feature rollouts: Test a plugin in one sub-project before rolling it out to others—no more big-bang deployments. Use case: If we’re standardizing our logging layer, we can now build @pmu/plugin-logger once and deploy it to all services. Or if we’re integrating a new payment provider, their SDK can live in a plugin without cluttering our main repo. Proposal: Let’s define 2–3 high-impact plugins (e.g., logging, queue workers) and measure the time saved vs. manual implementation. If it cuts our onboarding time by 30%, we’ve got a clear win."*