Marshaller Bridge Laravel Package

Technical Evaluation

Architecture Fit

• Purpose Alignment (Unchanged): The spiral/marshaller-bridge package remains Spiral Framework-specific, offering no inherent advantage for Laravel’s native marshalling needs (DTOs, API responses, or serialization). Laravel’s ecosystem (spatie/laravel-data, Fractal, Symfony Serializer) continues to provide better alignment with Laravel’s architecture.

• Spiral vs. Laravel Ecosystem (Updated Context):

  • The package’s lack of Laravel compatibility persists, despite minor dependency updates (e.g., actions/checkout bump).
  • No new Laravel-specific features introduced in v1.0.1.
  • Spiral’s marshalling abstractions (MarshallerInterface) remain incompatible with Laravel’s DI container and Eloquent/Blade integrations.

Integration Feasibility (Unchanged)

• Marshalling Needs (Reiterated):

  • No evidence of Laravel-specific optimizations (e.g., Eloquent model support, Blade templating).
  • No service provider or facade for Laravel, requiring manual wiring.
  • Last release (2023-10-05) with no Laravel-focused updates in v1.0.1.

• Key Dependencies (Updated):

  • Minor dependency updates (e.g., actions/checkout) are CI/CD tooling changes and irrelevant to Laravel integration.
  • No changes to core marshalling logic or Spiral dependencies.

Technical Risk (Updated)

Key Questions (Updated)

1. Why Spiral? (Reiterated)

   • New sub-question: Does the CI/CD update (actions/checkout) imply any future Laravel support? (Answer: No—this is a Spiral repo maintenance change.)

2. Migration Path (Reiterated)

   • Clarification: Would a custom Laravel adapter for Spiral’s MarshallerInterface be viable? (Answer: Only if Spiral’s marshalling logic is absolutely required and no Laravel alternative exists.)

3. Alternatives (Reiterated)

   • New consideration: Has spatie/laravel-data or Fractal recently added features that obviate Spiral’s marshalling? (Answer: Yes—both are actively maintained and Laravel-native.)

4. Long-Term Viability (Updated)

   • Critical: The lack of updates since 2023-10-05 and no Laravel engagement suggest no future viability.
   • New risk: If Spiral’s marshalling layer changes, this package will break without Laravel-specific fixes.

Integration Approach

Stack Fit (Unchanged)

• Laravel’s Native Tools (Reiterated):
  • spatie/laravel-data (DTOs), Fractal (API responses), Symfony Serializer (flexible serialization) remain superior alternatives.
• Spiral Bridge Feasibility (Updated):
  • v1.0.1 adds no Laravel value: The actions/checkout update is CI/CD-only and irrelevant to integration.
  • Workaround feasibility: Still not recommended unless:
    • You’re migrating from Spiral to Laravel and need temporary parity.
    • You have internal Spiral expertise to maintain a custom bridge.

Migration Path (Unchanged)

1. Assessment Phase (Reiterated):
   • Audit marshalling use cases; compare with spatie/laravel-data or Fractal.
2. PoC Phase (Reiterated):
   • Test Spiral bridge in a non-critical module—expect failures in DI, Eloquent, or Blade contexts.
3. Fallback Plan (Reiterated):
   • Default to spatie/laravel-data or Fractal.
   • If Spiral logic is non-negotiable, extract a custom marshaller without the bridge.

Compatibility (Updated)

Sequencing (Unchanged)

1. Phase 1: Replace marshalling with spatie/laravel-data or Fractal.
2. Phase 2: If Spiral logic is required, build a custom Laravel service.
3. Phase 3: Only consider spiral/marshaller-bridge for full Spiral migration.

Operational Impact

Maintenance (Updated)

• High Risk (Worsened):
  • No Laravel-specific updates in v1.0.1; package appears abandoned for Laravel.
  • Spiral dependency: Future Spiral marshalling changes will break Laravel integration.
• Low-Risk Alternatives (Reiterated):
  • spatie/laravel-data (actively maintained, Laravel-native).
  • Fractal (mature, widely adopted).

Support (Updated)

• No Community (Unchanged):
  • 0 stars, no Laravel issues, no vendor support.
  • CI/CD update (v1.0.1) is irrelevant to Laravel support.
• Workarounds (Reiterated):
  • Fork and adapt (but unsustainable).
  • Open issues in Spiral Framework repo (but no Laravel-specific help).

Scaling (Unchanged)

• Performance Impact (Reiterated):
  • No Laravel benchmarks; expect no advantage over Fractal or spatie/laravel-data.
  • Risk: Extra Spiral abstractions may increase memory usage.
• Throughput (Reiterated):
  • No data to suggest this package improves scaling in Laravel.

Failure Modes (Updated)

Ramp-Up (Updated)

• Learning Curve (Unchanged):
  • High: Requires Spiral marshalling knowledge (unfamiliar to Laravel teams).
  • Low: Alternatives like spatie/laravel-data have Laravel-specific docs.
• Onboarding Time (Reiterated):
  • 1-2 weeks for PoC (if attempted), but high failure rate.
• Team Skills (Updated):
  • Spiral expertise is now a harder sell: With no Laravel updates in v1.0.1, this package is effectively dead for Laravel.
  • Recommendation: Use Laravel-native tools to avoid skill gaps.

Recommendation (Updated)

Do not use spiral/marshaller-bridge in Laravel. v1.0.1 introduces no meaningful changes for Laravel users.

Instead:

1. For DTOs: Use spatie/laravel-data (actively maintained).
2. For API responses: Use Fractal or Laravel’s built-in JSON responses.
3. For serialization: Use Symfony Serializer.

If Spiral-specific marshalling is absolutely required:

• **Extract logic into a custom