Base Bundle Laravel Package

Product Decisions This Supports

• Accelerating Symfony 3/4 Development: Reduces boilerplate for routing, service declarations, and parameter converters, enabling faster MVP delivery for internal tools or public-facing applications.
• Consistent Architecture: Enforces a service-based routing pattern (vs. traditional controller-based), aligning with microservices or modular design goals.
• Validation & Utility Standardization: Centralizes date parsing, translation logic, and validation rules, reducing duplication across bundles.
• Build vs. Buy: Justifies buying this lightweight package over custom solutions for teams already using Symfony, especially if they lack dedicated backend engineers.
• Roadmap for Legacy Systems: Ideal for modernizing older Symfony 3/4 codebases by abstracting repetitive configurations (e.g., routes, services).
• Non-Technical Stakeholder Buy-In: Simplifies handoffs between frontend and backend teams by decoupling routes from controllers (actions are services).

When to Consider This Package

• Avoid If:
  • Using Symfony 5+ (deprecated for newer versions; no active maintenance).
  • Requiring high-performance routing (adds minor abstraction overhead).
  • Needing complex controller logic (package favors stateless actions over traditional controllers).
  • Team prefers modern alternatives like API Platform, Symfony UX, or custom DTOs.
  • No Symfony ecosystem: If migrating from Laravel or another framework, evaluate framework-native solutions first.
• Look Elsewhere If:
  • Need real-time features (WebSockets, reactive programming) → Use Mercure or Symfony Messenger.
  • Requiring graphQL → Use API Platform or Envers.
  • Security-critical applications → Prioritize packages with active maintenance (e.g., Symfony SecurityBundle).

How to Pitch It (Stakeholders)

For Executives: "This package cuts Symfony setup time by 30%+ by automating repetitive routing and service configurations. For our [internal tool/public API], it lets our team focus on business logic instead of boilerplate—similar to how Laravel’s Eloquent saves dev time. Low risk (MIT license), zero vendor lock-in, and works with our existing Symfony stack. Estimated ROI: [X] hours saved in Q1."

For Engineers: *"SidusBaseBundle replaces manual YAML/annotation routing with service-based actions (e.g., FooBarBundle\Action\MyAction maps directly to /path). Key wins:

• No _controller clutter: Routes auto-resolve from service IDs.
• Validation/translation utilities: Centralized BaseLoader and TranslatorUtility reduce copy-paste.
• Compiler passes: Tag-based dependency injection (e.g., inject all @logger services into a handler). Tradeoff: Symfony 3/4 only, but perfect for [legacy system/modernization project]. Let’s prototype it in [Bundle X] by [date]."*

For Designers/Non-Technical Teams: "This change makes our backend more modular—routes and actions are now like ‘building blocks’ that can be rearranged without touching controllers. Think of it as Lego for APIs: easier to assemble, harder to break."