- Does shopware/dynamodb-dal-bundle work with Laravel?
- No. shopware/dynamodb-dal-bundle is a Shopware 6 bundle built on Symfony, not a Laravel package. It integrates with Shopware's Data Abstraction Layer and does not use Eloquent, Laravel's service container, or Laravel's queue and cache abstractions. If your application is Laravel, do not try to bridge this bundle in; use the AWS SDK for PHP behind your own repository interface instead.
- How do I install shopware/dynamodb-dal-bundle in Shopware 6?
- Install it with Composer in a Shopware 6 project and register the Symfony bundle in the Shopware container configuration. Then provide AWS region, credentials, and table settings, and provision the DynamoDB tables before first use. Because 0.7.1 fixed a missing baseline action from 0.7.0, run an install-and-smoke-test against the published artifact on every bump.
- What Laravel version does this package support?
- This package does not support any Laravel version because it is not a Laravel package. It targets Shopware 6 and Symfony service wiring, so Laravel version constraints are irrelevant. For Laravel DynamoDB persistence, evaluate the AWS SDK for PHP directly rather than a Shopware bundle.
- How do I configure AWS region and credentials for the DynamoDB DAL bundle?
- Configure the AWS region, credentials, and table settings through the bundle's Symfony/Shopware configuration. You also need to decide which DAL entities route to DynamoDB versus the relational store, because that choice drives key design and index planning. Check the package's composer.json for the AWS SDK and Doctrine DBAL versions it pins before committing.
- Can I use Amazon DynamoDB as an Eloquent driver in Laravel?
- Laravel has no built-in DynamoDB driver for Eloquent, and this bundle does not provide one. A practical Laravel approach is to define a repository interface, implement it with the AWS SDK for PHP, and keep DynamoDB key design explicit. That path is smaller, testable, and stays inside Laravel/PHP competency.
- Is shopware/dynamodb-dal-bundle production-ready?
- Treat it as experimental. The package is pre-1.0 at 0.7.x, has a thin maintainer base, and gives no SemVer compatibility guarantee across minor releases. Swapping the DAL backing store is also a one-way door for migrated entities, so validate with a sandbox and a rollback plan before production use.
- How do I test the bundle locally without hitting AWS?
- Use DynamoDB Local for local development and CI, and run a sandbox spike on a scratch Shopware instance against a low-value, high-write entity. Define the table schema and GSIs from real query patterns rather than relying on bundle defaults. Also verify the installed artifact, since 0.7.0 shipped without a baseline action that 0.7.1 added.
- Which Shopware entities should I move to DynamoDB first?
- Start with a low-value, high-write entity that has simple access patterns and no cross-entity transaction requirements. Define primary keys and GSIs explicitly for each entity you move, because DynamoDB single-table modeling is driven by reads, not by the relational schema. Avoid moving entities whose workflows depend on relational joins or multi-entity transactions.
- How do I migrate existing Shopware data from MySQL to DynamoDB?
- There is no documented supported backfill or rollback path in the package context, so plan your own migration. Use a strangler approach: spike in a sandbox, define the DynamoDB schema, backfill existing rows with a purpose-built script, and keep the relational store authoritative until reads and writes are verified. Data written to DynamoDB is not trivially reconciled back into MySQL.
- What are the alternatives to shopware/dynamodb-dal-bundle for Laravel?
- For Laravel, the realistic alternative is direct AWS SDK for PHP integration behind a repository interface, not this Shopware bundle. For Shopware 6, evaluate whether DynamoDB is appropriate for the specific entity and query patterns before adopting the bundle. Other alternatives include keeping Doctrine DBAL on MySQL and using DynamoDB only for auxiliary high-scale workloads.