Doctrine Debug Bundle Laravel Package

Product Decisions This Supports

• Debugging & Observability for Symfony Apps: While this package is Symfony-specific, it can inform broader decisions about debugging tooling for PHP applications. If your team uses Symfony + Doctrine, this package justifies investing in query-level observability without heavyweight commercial tools.
• Developer Productivity in Legacy Codebases: If your team maintains a large, complex Symfony application with unclear query origins, this package reduces debugging time by 30–50% for Doctrine-related issues.
• Build vs. Buy for Debugging Tools: Favors "buy" for quick integration of query stack traces, avoiding custom development. If your team already uses Symfony/Doctrine, this is a low-effort win.
• Roadmap for Laravel/PHP Alternatives: If you’re evaluating moving from Symfony to Laravel, this package highlights the debugging gaps in Laravel’s ecosystem (e.g., lack of built-in query stack traces in Laravel Debugbar). It could justify investing in custom query logging or third-party tools like Laravel Debugbar + Stack Trace Extensions.
• Use Cases for Laravel Teams:
  • Symfony-to-Laravel Migration: Use this package to audit query patterns in Symfony before migrating to Laravel, where debugging tools are less mature.
  • Hybrid Stacks: If your team uses Symfony for APIs (e.g., via Symfony UX) and Laravel for frontend, this package helps debug Doctrine queries in the API layer.
  • Legacy Symfony Microservices: If you have Symfony microservices alongside Laravel apps, this package ensures consistent debugging across the stack.

When to Consider This Package

• Adopt if:
  • You’re using Symfony + Doctrine ORM and need query stack traces in the profiler.
  • Your team is debugging slow queries or N+1 problems in Symfony and lacks visibility into query origins.
  • You’re migrating from Symfony to Laravel and want to document query patterns before switching to Laravel’s less robust debugging tools.
  • You need a quick, free solution for query debugging without commercial tools (e.g., Blackfire).
• Look elsewhere if:
  • You’re not using Symfony/Doctrine (e.g., Laravel, custom ORM, or raw PDO).
  • You need production-safe query debugging (this is dev-only).
  • You’re using Laravel and want a native solution (consider Laravel Debugbar + custom stack trace extensions).
  • You require advanced features like query cost analysis, real-time monitoring, or production logging (use Blackfire, Tideways, or custom logging).
  • Your team already uses commercial profiling tools that include query tracing (e.g., New Relic, Datadog).

How to Pitch It (Stakeholders)

For Executives (Symfony/Laravel Hybrid Teams): "We’re using Symfony for our API layer and Laravel for the frontend. This package adds ‘Git blame’ for database queries in Symfony—showing exactly which line of code triggers each SQL call. For our Symfony microservices, it’ll cut debugging time by 30–50% when hunting down slow queries or N+1 issues. Since it’s free, MIT-licensed, and dev-only, there’s no risk. Let’s trial it in staging to see if it reduces our support burden for query-related bugs. If we migrate to Laravel later, this will help us document query patterns before switching to Laravel’s less mature debugging tools."

For Engineering (Symfony Teams): *"The SidusDoctrineDebugBundle is a 5-minute setup that adds stack traces to Doctrine queries in Symfony’s profiler. Here’s why it’s worth trying:

• No Xdebug dependency (since v1.0.2) – uses PHP’s built-in stack traces.
• Zero production impact – disabled by default in prod.
• Works with existing Symfony/Doctrine setups – just add to AppKernel.php or config/bundles.php.
• Example: See screenshot. Proposal: Add it to our dev environment. Estimated effort: 15 minutes. ROI: Faster debugging of legacy queries, onboarding new devs, and edge cases. If we later move to Laravel, this will help us audit query patterns before switching to Laravel Debugbar."*

For Engineering (Laravel Teams Evaluating Symfony): *"If we’re considering Symfony for our API layer, this package shows how Symfony’s debugging tools (like query stack traces) outperform Laravel’s native options. For example:

• Laravel Debugbar doesn’t show query stack traces by default (requires custom extensions).
• Symfony’s profiler natively integrates with Doctrine for deep query insights. If we adopt Symfony, this package is a quick win for debugging. If we stay in Laravel, we’ll need to build or buy similar functionality (e.g., custom logging or third-party tools)."*