- Does rikudou/psr6-dynamo-db-bundle work with Laravel out of the box?
- No. It is a Symfony bundle that relies on Symfony dependency-injection and bundle conventions, and Laravel has no native bundle loader. The reusable part is the underlying PSR-6/PSR-16 DynamoDB cache pool, which you can wrap in a custom Laravel cache store. Plan for a small integration layer rather than a drop-in driver.
- How do I install rikudou/psr6-dynamo-db-bundle in a Laravel project?
- You can install it with Composer, but Symfony auto-discovery will not register it in Laravel. You still need a service provider and a cache store adapter backed by the package's PSR-6 or PSR-16 pool. Version 4.2.0 also requires at least version 3.2 of the base cache library, so review that library's changelog separately.
- Which Laravel and PHP versions does this DynamoDB cache package support?
- The package declares Symfony support, not Laravel support, so no Laravel version range is promised. Its v4.2.0 release adds Symfony 8 support, which does not affect Laravel compatibility. Check Composer constraints for PHP and the AWS SDK, and treat Laravel support as something you provide through your own adapter.
- Can I use DynamoDB as a Laravel cache backend with this bundle?
- Yes, DynamoDB can serve as a shared, persistent cache for stateless containers, Laravel Vapor/Lambda, and multi-instance workloads. However, Laravel's cache contract is Illuminate\Contracts\Cache\Store and Repository, not PSR-6 or PSR-16. You need a custom adapter that maps Laravel cache operations onto the package's pool. Keep Redis or Memcached for hot, low-latency paths.
- How do I configure AWS credentials and a DynamoDB table for this cache?
- The bundle provides configuration for AWS and DynamoDB table settings, which you would translate into Laravel config and pass to the underlying AWS client. Prefer IAM roles over hard-coded keys, and keep the table in the same region as your application. Confirm the expected table schema, capacity mode, and IAM permissions before deploying.
- Does this package support atomic increment, decrement, and locks for Laravel?
- Atomicity is a known gap to verify, not a documented guarantee. The package is a PSR-6 cache pool, and Laravel's atomic increment/decrement and lock behavior are part of the Illuminate cache contract, not PSR-6. Test increment, decrement, conditional writes, and lock semantics against your adapter before using them for counters, rate limiting, or idempotency.
- How does TTL and cache expiry work with DynamoDB?
- DynamoDB TTL deletion is eventual, so expired items may still be returned unless the adapter filters them on read. Validate TTL behavior, flush, and key normalization in your integration tests. Do not assume Redis-style immediate expiry.
- Can I test this bundle with DynamoDB Local?
- The provided release notes do not document DynamoDB Local support, but AWS SDK clients can usually be pointed at a local endpoint. Verify whether the underlying cache library allows endpoint overrides before relying on it in CI. If not, use integration tests against a dedicated AWS table with strict cleanup.
- What are the alternatives to this Symfony DynamoDB cache bundle for Laravel?
- You can build a custom Laravel cache store directly on the AWS SDK, or use a community DynamoDB cache driver if one fits your constraints. For hot caches, locks, sessions, queues, and rate limits, Redis or Memcached remain safer defaults. Choose DynamoDB when you need a managed, persistent, cross-instance cache and can tolerate higher latency and per-request cost.
- Is rikudou/psr6-dynamo-db-bundle production-ready and maintained?
- Adoption signals are low, with around 20 stars and zero dependents, and the project is likely single-maintainer. The v4.2.0 release is mainly Symfony 8 support plus a base-library floor of 3.2, and the 3.2 changes are not described in the bundle notes. Pin versions, review the base library changelog, and pilot in an isolated workload before making it a production default.