Mandango Bundle Laravel Package

Product Decisions This Supports

• Build-vs-buy for MongoDB persistence: This bundle is a glue layer for Mandango, a MongoDB ODM. The real PM question is "Do we adopt an ODM and which one?" — and the answer here is Doctrine MongoDB ODM, not Mandango. Treat this package as a data point on the "wrong side" of that decision.
• Framework-fit due diligence: The brief frames this as a Laravel/PHP package, but it is a Symfony2 bundle. The most valuable decision it drives is a screening decision: confirming that a dependency is the wrong framework target before a team invests a sprint on it. Zero Laravel service providers, facades, or config files exist here.
• Legacy triage on inherited codebases: If your team acquired or inherited a PHP/Mongo application, this package is a fingerprint of the app's vintage and your migration scope. It belongs on the tech-debt backlog with a named owner, not the roadmap.
• Roadmap risk call: 25 stars, 0 dependents, Symfony2-only, and an underlying ODM that predates PHP 7 make this a "sunset, don't adopt" line item.
• Not a decision it supports: greenfield feature work, scaling decisions, vendor risk management, or anything requiring a support contract. There is no support story, no hiring pool, and no active maintenance to buy into.

When to Consider This Package

Consider it only when:

• You are maintaining an existing Symfony 2.x application already built on Mandango and need the bundle's wiring to keep the lights on for a short, time-boxed period.
• You need to reproduce or understand an old deployment for audit or archival purposes.
• The work is internal, non-customer-facing, and engineering has explicitly accepted the maintenance risk with a named owner.

Look elsewhere when:

• Any new project, Laravel or otherwise. For Laravel + MongoDB use mongodb/laravel-mongodb (Eloquent-style); for a document mapper use doctrine/mongodb-odm. Both are maintained, PHP 8 compatible, and have real install bases.
• You are on any Symfony beyond 2.x. This bundle targets Symfony2-era APIs and is not a forward path.
• You are on PHP 7.0+. The underlying Mandango relies on the removed ext-mongo extension; modern PHP cannot load it without a driver-layer rewrite. Assume a hard blocker until a spike proves otherwise.
• You need community support, documentation, security review, a hiring pool, or an SLA. Zero dependents and 25 stars mean no ecosystem. There is nobody to call.
• You want a long-lived product surface. The dependency chain (Mandango → legacy driver era → EOL Symfony) is the wrong foundation to build on.

How to Pitch It (Stakeholders)

To executives: This is a legacy integration shim, not a strategic component — and importantly, it is a Symfony2 bundle, not a Laravel package, so it does not fit our current stack. It has minimal adoption (25 stars, zero dependent packages), targets an end-of-life framework, and sits on top of a MongoDB ODM that is no longer maintained and depends on a PHP extension removed in PHP 7. Recommendation: do not adopt. If MongoDB persistence is the actual requirement, we should standardize on the maintained alternative (mongodb/laravel-mongodb for Eloquent-style work, or Doctrine MongoDB ODM for a document-mapper approach). If it already exists in production, classify it as end-of-life technical debt with a funded, dated migration to the mainstream option — the mainstream path is maintained, PHP 8 compatible, and easy to staff.

To engineering: Treat this as a false positive on stack fit. The bundle ships Symfony DI wiring, YAML config under a mandango key, and Mondator codegen commands — none of which Laravel can consume. Even the underlying mandango/mandango library is blocked by the ext-mongo removal and has no upstream triage. Do not invest beyond a 1–2 day timeboxed spike, and expect that spike to fail at the extension-install step. For any MongoDB work in Laravel, substitute mongodb/laravel-mongodb (near-zero ramp-up given Eloquent fluency) and close the request. If a legacy Symfony2/Mandango system exists, freeze and pin it, export data via the modern driver, and fund a timeboxed exit plan rather than any new integration work. The decision to make now is not "which bridge" but "when do we retire Mandango" — and who owns that date.