Pomm Symfony Bridge Laravel Package

Technical Evaluation

Architecture Fit

• Updated Purpose Alignment:
  • The 6.0.0 release now exclusively targets Symfony 8, aligning with its LTS roadmap (2024–2027). This makes it a strong fit for:
    • Symfony 8 monoliths/microservices with PostgreSQL-heavy workloads.
    • Teams migrating to Symfony 8 or adopting Pomm for query optimization.
  • Deprecation Risk: Apps on Symfony <8 (e.g., 6.4/7.x) cannot use this version without a full Symfony upgrade.
  • Non-Fit Scenarios (unchanged):
    • Non-Symfony stacks (Lumen, Slim).
    • Non-PostgreSQL databases.
    • Simple CRUD apps with minimal query complexity.

Integration Feasibility

• Symfony 8 Dependency:
  • Hard Requirement: Symfony 8.x (no backward compatibility with 6/7).
  • Impact:
    • Breaking: Apps on older Symfony versions must upgrade (major effort).
    • Opportunity: Forces alignment with Symfony’s latest features (e.g., PHP 8.2+).
  • Middleware Changes:
    • Symfony 8’s HttpKernel updates may require adjustments to the profiler’s event listeners.
• Pomm ORM Compatibility (unchanged):
  • Still requires Pomm 2.x+ as the primary ORM. No changes to this constraint.

Technical Risk

Key Questions (Updated)

1. Is Symfony 8 adoption planned? If not, can this package wait for a Symfony 7-compatible release?
2. What’s the current Symfony version? (Critical blocker if <8.)
3. Is Pomm already in use? (Unchanged, but now tied to Symfony 8 upgrade path.)
4. How critical is real-time query analysis? (Overhead may be justified for Symfony 8’s performance gains.)
5. Who owns the Symfony 8 upgrade? (DevOps vs. backend team alignment needed.)

Integration Approach

Stack Fit (Updated)

• Primary Use Case:
  • Symfony 8 + Pomm stacks where query performance is critical (e.g., high-traffic APIs, reporting).
  • PostgreSQL-heavy apps with complex queries.
• Secondary Use Case:
  • Symfony 8 monoliths migrating from Doctrine/PDO to Pomm for better profiling.
• Non-Fit Stacks (Updated):
  • Symfony <8: Incompatible without upgrade.
  • Microservices using gRPC: Profiling may conflict with OpenTelemetry.
  • PHP <8.2: Hard blocker (Symfony 8 requirement).

Migration Path (Updated)

1. Pre-Upgrade Assessment:
   • Audit Symfony version (must be 8.x).
   • Benchmark current profiling tools (e.g., Blackfire) vs. Pomm’s profiler.
2. Symfony 8 Upgrade Path:
   • Follow Symfony’s upgrade guide (major effort).
   • Test Pomm compatibility in Symfony 8’s new HttpKernel.
3. PoC Phase:
   • Install conserto/pomm-symfony-bridge:6.0.0 in a Symfony 8 dev environment.
   • Instrument a high-complexity endpoint and compare with existing tools.
4. Full Integration:
   • Step 1: Update composer.json:

     - "symfony/*": "^6.4",
     + "symfony/*": "^8.0",
     + "conserto/pomm-symfony-bridge": "^6.0"
     

   • Step 2: Configure Pomm profiler in config/packages/pomm.yaml (Symfony 8’s new config system):

     pomm:
         profiler:
             enabled: true
             storage: symfony_cache  # Recommended for Symfony 8
     

   • Step 3: Extend Symfony’s WebProfilerBundle (updated for Symfony 8) to display Pomm metrics.
   • Step 4: Disable in production via APP_ENV=prod or feature flags.

Compatibility (Updated)

• Symfony Versions:
  • Only Symfony 8.x (no downgrade support).
  • PHP 8.2+ required (Symfony 8 mandate).
• Pomm Versions:
  • Still Pomm 2.x+, but test with latest stable (e.g., 2.10+).
• Dependencies:
  • New Conflicts:
    • Symfony 8’s updated bundles (e.g., framework-bundle) may need config adjustments.
    • PHP 8.2 features (e.g., typed properties) may require Pomm updates.

Sequencing (Updated)

1. Prerequisites:
   • Symfony 8 upgrade (non-negotiable).
   • Pomm as primary ORM (no mixed Doctrine/Pomm).
2. Order of Operations:
   • Dev/Staging: Enable profiling for all environments post-upgrade.
   • CI/CD: Add Pomm profiler to Symfony 8’s test suite (e.g., fail builds for slow queries).
   • Production: Enable selectively (e.g., admin routes only) via env vars.
3. Rollback Plan:
   • Revert to conserto/pomm-symfony-bridge:5.0.1 (Symfony 7 compatible).
   • Fallback to Blackfire or PostgreSQL’s pg_stat_statements.

Operational Impact

Maintenance (Updated)

• Proactive Tasks:
  • Quarterly: Update to latest 6.x releases and patch Symfony 8 dependencies.
  • Annual: Review profiler data for Symfony 8-specific regressions (e.g., new query patterns).
• Reactive Tasks:
  • Symfony 8 Alerts: Monitor for deprecation warnings in Pomm/Symfony 8.
  • Query Refactoring: Use profiler to optimize for Symfony 8’s improved HTTP cache.

Support (Updated)

• Troubleshooting:
  • Symfony 8-Specific Issues:
    • Profiler not loading → Check symfony/framework-bundle config.
    • PHP 8.2 warnings → Update Pomm to latest stable.
  • Tools:
    • Symfony 8’s new Profiler UI (may require Pomm metric integration).
    • Xdebug 3.2+ for debugging Pomm queries in Symfony 8.
• Team Skills:
  • Symfony 8 internals (e.g., new event system).
  • PHP 8.2 features (e.g., enums, read-only properties).

Scaling (Updated)

• Performance Impact:
  • Symfony 8 Optimizations: May reduce overhead (e.g., faster HttpKernel).
  • Memory: Use symfony_cache storage to avoid bloat.
• Horizontal Scaling:
  • Stateless: Profiler data is request-scoped; no shared storage needed.
  • Edge Cases: High-cardinality queries may still bloat cache (monitor symfony_cache).
• Cost:
  • No direct costs, but Symfony 8 upgrade may require cloud provider updates (e.g., PHP 8.2 support).

Failure Modes (Updated)