Weave Code
Connection Bundle Laravel Package
kitano/connection-bundle
Symfony bundle for managing multiple database connections. Configure named connections, switch between them at runtime, and centralize connection setup—useful for multi-tenant apps or services that need to talk to more than one database.
Directed graph implementation to create any connection between two objects (ie. follower/following relation in a social network)
Frequently asked questions about Connection Bundle
- Is kitano/connection-bundle a Laravel package?
- No. It is a Symfony bundle that adds a connection layer between Doctrine entities, with Symfony kernel glue, DI configuration, and Doctrine ORM mappings. Only the non-Symfony domain core—the connection manager, repository, and edge entity—is portable to Laravel, and that port is a separate effort rather than a Composer install.
- Can I install kitano/connection-bundle in Laravel with Composer?
- A normal composer require will not work on a modern Laravel stack. The bundle is built for Symfony and its PHP 5.x-era Composer constraints are likely to hard-conflict with a PHP 8.1+ Laravel baseline. Treat it as a reference implementation, not a runtime dependency; run a version gate on composer.json before planning any integration.
- How do I install and configure Kitano Connection Bundle in Symfony?
- In Symfony you install it through Composer, register the bundle in the kernel, and configure named connection types through the DI extension. The bundle then uses Doctrine ORM mappings to persist connections and exposes the connection manager as a service. Check the repository's composer.json and README first because the project is dormant and release metadata may be incomplete.
- Does kitano/connection-bundle support Laravel 10 or Laravel 11?
- No. The package ships no Laravel service provider, no Eloquent models, and no publishable Laravel config, so it cannot be used as a Laravel 10 or Laravel 11 dependency out of the box. Supporting those versions would require porting the manager and repository into an internal Eloquent package. No maintained Laravel fork is indicated in the project signals.
- What are the best alternatives to Kitano Connection Bundle for Laravel?
- For simple relationships, Laravel's native polymorphic relationships such as morphToMany and morphMany are usually the right first choice. For typed, directed, attributed edges, build a small edge table with source_type, source_id, target_type, target_id, type, meta, and created_at, then add a BFS walk with a visited set and max-depth guard. That in-house approach is often cheaper and safer than reviving 2015-era Symfony code.
- How do I link and unlink Doctrine entities using the connection manager?
- The bundle provides a central connection manager service that links and unlinks arbitrary Doctrine entities, plus repository query helpers for retrieving connections and related objects. This keeps relationship logic out of your domain models and lets you define configurable connection types. In Laravel, the equivalent would be a service or action layer around an Eloquent edge model, because the Symfony service wiring does not carry over.
- Does kitano/connection-bundle work on PHP 8 with modern Doctrine ORM?
- That is unlikely without work. The Composer constraints are PHP 5.x-era and the package is coupled to Symfony and Doctrine ORM, so modern PHP 8 and current Doctrine releases may not resolve. Verify the actual composer.json pins and run the test suite, if one exists, on PHP 8.x before considering any reuse.
- How does Kitano Connection Bundle perform for deep graph traversals and N+1 queries?
- The design does not guarantee cycle detection, and traversal may query per hop, so N+1 behavior and query count can grow with depth. Polymorphic edges also cannot carry real foreign keys, which can leave orphan rows when entities are deleted. Benchmark a depth-3 expansion against a seeded edge table and measure worst-case query count before trusting it in production.
- Is kitano/connection-bundle maintained and safe for production use?
- The maintenance signals are weak: around 13 stars, zero dependents, no release cadence, and a dormant vendor. That means no CVE response path, no maintainer to escalate to, and no peer community to compare notes with. If you adopt it, vendor it under your organization namespace, assign an owner, verify the license, and add CI and tests, or build the edge model in-house.
- How should I test, benchmark, or port Kitano Connection Bundle into Laravel?
- Start with a version gate by reading composer.json; if its PHP and Symfony constraints conflict with your baseline and no maintained fork exists, stop before porting. Then run a two-to-three-day spike: read the manager and repository code, count lines outside the Symfony layer, and benchmark a depth-3 walk over seeded data. For a real port, strip the Bundle class and DI extension, migrate Doctrine mappings to Eloquent, add a service provider with singleton bindings and publishable config, and stand up CI. Avoid a temporary Doctrine-plus-Eloquent bridge because it tends to become permanent.
Weaver
How can I help you explore Laravel packages today?