Weave Code
Riak Bundle Laravel Package
kbrw/riak-bundle
A Symfony bundle that integrates Riak into PHP applications, providing configuration and service wiring for connecting to and working with Riak data stores.
Symfony Bundle used to communicate with Riak distributed database
Frequently asked questions about Riak Bundle
- Can I install kbrw/riak-bundle in a Laravel application?
- You can run Composer require, but the package is a Symfony bundle and will not register itself in Laravel. Laravel uses service providers and its own config repository, not Symfony's bundle system or DI container. Plan to instantiate the underlying Riak PHP client through a thin Laravel service provider instead.
- What is kbrw/riak-bundle used for?
- It is a Symfony bundle that integrates Riak into PHP applications by providing configuration and service wiring for Riak connections. It targets Symfony's bundle system, dependency injection container, and configuration tree. It is not a Laravel package and does not provide Laravel service providers or facades.
- How do I configure Riak in Laravel if I must use this bundle?
- Do not rely on the bundle's Symfony configuration tree inside Laravel. Create a Laravel service provider that instantiates the Riak PHP client directly, mapping values from config/riak.php or environment variables. Wrap the client behind a repository interface so application code is not coupled to the bundle.
- Which Laravel and PHP versions are supported by kbrw/riak-bundle?
- The package does not officially support Laravel at all. It appears to be legacy Symfony 2 or 3 era code, so its Composer constraints may conflict with modern Laravel versions and PHP 8.1 or newer. Verify compatibility in an isolated Composer spike before committing to it.
- Is kbrw/riak-bundle maintained and safe for production?
- The package has very low adoption, with roughly 15 stars and zero dependents, and shows signs of being unmaintained. Using it inside Laravel means your team owns the adapter, dependency pinning, and compatibility checks. Treat it as a reference implementation rather than a production dependency.
- What are alternatives to kbrw/riak-bundle for Laravel?
- If Riak is mandatory, use the underlying Riak PHP client directly through a Laravel service provider and wrap it in a repository abstraction. If Riak is not strategic, consider Redis, DynamoDB, or MongoDB behind the same repository interface. That keeps migration open and avoids tying Laravel to a Symfony bundle.
- How do I test a Laravel integration with Riak?
- Run integration tests against a real Riak cluster because eventual consistency and node availability cannot be simulated reliably with mocks. Unit test your repository abstraction with fakes for application logic. Include timeout, retry, and connection lifecycle checks, and roll out behind a feature flag.
- Why does kbrw/riak-bundle fail to load in Laravel?
- The package depends on Symfony's bundle system, DI container, and configuration tree, none of which Laravel loads. Its service definitions and extension classes are not a Laravel integration surface. The Symfony DI assumptions are usually the first failure point when trying to use it in Laravel.
- Can I use kbrw/riak-bundle with Laravel 11 or PHP 8.2?
- It is not recommended without a compatibility spike. The package's legacy Symfony constraints may conflict with Laravel 11 and PHP 8.2, and abandoned dependencies can block upgrades. A thin Laravel service provider around a maintained Riak client is the safer path.
- What should I check before adopting kbrw/riak-bundle in a Laravel project?
- First confirm that Riak is mandated, including the Riak KV version and whether the HTTP or protobuf API is used. Then check whether the underlying Riak PHP client is maintained and run an isolated Composer spike against your Laravel and PHP matrix. Finally, plan a repository abstraction, integration tests against a real cluster, and clear ownership of Riak operations.
Weaver
How can I help you explore Laravel packages today?