Stripe Bundle Laravel Package

Technical Evaluation

Architecture Fit

• Symfony2 Bundle Focus: The package is a Symfony2-specific bundle, which may introduce tight coupling with legacy Symfony2 architecture if the project is on Symfony 4/5/6+ or Laravel. A Laravel TPM would need to assess whether:
  • The bundle can be adapted via a Symfony bridge (e.g., symfony/console, symfony/http-foundation).
  • A rewrite is needed to abstract Symfony dependencies (e.g., Doctrine ODM, FOSUserBundle).
  • Alternative Laravel packages (e.g., spatie/laravel-stripe) should be prioritized instead.
• Stripe Integration: The core functionality (subscriptions, payments, invoices) aligns well with Laravel’s payment ecosystem, but the Symfony-specific abstractions (e.g., Doctrine ODM, FOSUser) may require significant refactoring.
• MongoDB Dependency: The bundle hardcodes MongoDB ODM, which is non-standard in Laravel (Eloquent/Query Builder is default). This could complicate migration unless the project already uses MongoDB.

Integration Feasibility

• High for Symfony2 Projects: If the project is Symfony2-based, integration is straightforward (follows documented steps).
• Moderate for Laravel with Symfony Bridge: Possible but non-trivial—would require:
  • Symfony components (e.g., symfony/console, symfony/http-kernel) to be installed.
  • Doctrine ODM → Eloquent mapping (custom ORM layer).
  • FOSUserBundle → Laravel Auth adaptation (e.g., laravel/breeze, spatie/laravel-permission).
• Low for Pure Laravel: The bundle’s Symfony-centric design makes it a poor fit without heavy modification. A native Laravel package (e.g., laravel-cashier) would be preferable.

Technical Risk

Key Questions for the TPM

1. Is Symfony2 a hard requirement, or can we migrate to Laravel?
   • If Laravel is the goal, this bundle may not be worth the effort.
2. Does the project already use MongoDB/Doctrine ODM?
   • If not, the migration cost increases significantly.
3. Are there existing Stripe integrations in the codebase?
   • If yes, assess overlap/conflicts with this bundle.
4. What’s the team’s familiarity with Symfony vs. Laravel?
   • Symfony expertise reduces integration risk.
5. Is the bundle’s WIP status acceptable?
   • Consider forking or waiting for updates if critical features are missing.
6. Are there Laravel-native alternatives with better support?
   • Example: laravel-cashier, spatie/laravel-stripe.

Integration Approach

Stack Fit

Migration Path

Option 1: Full Rewrite for Laravel (Recommended)

1. Replace Symfony Dependencies:
   • Drop Doctrine ODM → Use Eloquent or MongoDB PHP driver.
   • Replace FOSUser → Use Laravel Auth (laravel/breeze).
2. Abstract Stripe Logic:
   • Use spatie/laravel-stripe or laravel-cashier as a base.
   • Port bundle features (plans, subscriptions, hooks) into Laravel services.
3. Routing & Controllers:
   • Replace Symfony routing (routing.yml) with Laravel routes.
   • Convert Twig templates to Blade.
4. Hooks System:
   • Replace Symfony events with Laravel events/listeners.

Option 2: Symfony Bridge (High Effort)

1. Install Symfony Components:

   composer require symfony/console symfony/http-foundation symfony/dependency-injection
   

2. Create a Symfony Kernel:
   • Boot Symfony components in Laravel’s bootstrap/app.php.
3. Adapt the Bundle:
   • Override Doctrine ODM with Eloquent.
   • Mock FOSUser dependencies.
4. Risk: High maintenance overhead; not recommended unless Symfony2 is mandatory.

Option 3: Use Native Laravel Packages

• Laravel Cashier (for subscriptions):

  composer require laravel/cashier stripe/stripe-php
  

• Spatie Stripe:

  composer require spatie/laravel-stripe
  

• Pros: Lower risk, better Laravel integration.
• Cons: May require custom logic for bundle-specific features (e.g., plan management).

Compatibility

Sequencing

1. Assess Feasibility:
   • Decide between rewrite, bridge, or native Laravel.
2. Prototype Core Features:
   • Test Stripe subscriptions with laravel-cashier.
   • Validate plan management with Spatie.
3. Migrate Incrementally:
   • Start with auth + Stripe (lowest risk).
   • Gradually replace bundle features (e.g., invoices, hooks).
4. Deprecate Bundle:
   • Phase out Symfony dependencies as Laravel features replace them.

Operational Impact

Maintenance

Support

• Symfony2 Bundle:
  • Limited community support (16 stars, WIP).
  • No Laravel-specific help available.
• Laravel Native:
  • Active GitHub issues for Cashier/Spatie.
  • Stack Overflow/Laracasts resources available.
• Recommendation: Prioritize Laravel-native solutions for long-term support.

Scaling

• Performance:
  • Stripe API calls are the bottleneck (not the bundle).
  • MongoDB vs. MySQL: Eloquent (MySQL