Core Dam Bundle Laravel Package

Technical Evaluation

Architecture Fit

• DAM Core Bundle Alignment: The package is a Digital Asset Management (DAM) bundle built for Laravel/Symfony, offering asset metadata processing, Elasticsearch integration, bulk operations, and media distribution (images, videos, podcasts). It aligns well with media-heavy applications requiring scalable asset storage, search, and distribution.
• Modular Design: The bundle follows a facade-based architecture (e.g., AssetFacade, AssetFileFacade) with event-driven workflows (e.g., AssetMetadataBulkEventDispatcher), making it extensible for custom asset types (images, videos, podcasts).
• Elasticsearch Dependency: Heavy reliance on Elasticsearch for search and indexing introduces coupling but enables fast, faceted search (e.g., by metadata, authors, licenses).
• Microservice-Friendly: Supports Pub/Sub notifications (Google PubSub) and external system integrations (e.g., JWPlayer, YouTube), making it suitable for distributed architectures.

Integration Feasibility

• Laravel/Symfony Compatibility:
  • Requires Symfony 7.3+ and PHP 8.3+, which may necessitate upgrades if the current stack is older.
  • Uses Doctrine ORM 3+, Messenger component, and Monolog for logging.
  • Docker support via DOCKER_COMPOSE_SERVICE_NAME suggests containerized deployment is a best practice.
• Database Schema:
  • Introduces custom entities (Asset, AssetFile, Podcast, Distribution, LicenceGroup, etc.) with indices (e.g., IDX_licence_created_at).
  • MongoDB 2.0+ support via anzusystems/common-bundle may require hybrid DB setup if not already in use.
• Media Processing:
  • Leverages Vips/FFmpeg for image/video optimization (e.g., optimal resizes quality set to 90).
  • Supports AVIF, WebP, and animated GIFs, requiring server-side image processing (not just client-side).
• APIs & Workflows:
  • Provides SYS APIs for asset operations (e.g., create image from URL, bulk metadata updates).
  • Job-based processing (e.g., JobImageCopy, JobAuthorCurrentOptimize) for asynchronous tasks, reducing latency.

Technical Risk

Key Questions for Stakeholders

1. Search Requirements:

   • Is Elasticsearch already in use, or is this a new dependency? If new, what are the scaling plans (e.g., managed service vs. self-hosted)?
   • Are there custom search filters needed beyond what the bundle provides (e.g., fuzzy matching, synonyms)?

2. Media Processing:

   • What is the expected volume of media uploads? Are batch processing or parallel workers required?
   • Should fallback formats (e.g., JPEG for AVIF) be supported for broader compatibility?

3. Integration with Existing Systems:

   • Are there legacy DAM systems or CDNs that need to be synced with this bundle?
   • What external APIs (e.g., YouTube, JWPlayer) are already integrated, and which need new adapters?

4. Compliance & Licensing:

   • How will asset licensing (e.g., LicenceGroup, AssetLicence) be enforced in workflows?
   • Are there GDPR/CCPA requirements for author metadata or deletion workflows?

5. Operational Readiness:

   • What is the SLA for media processing (e.g., max wait time for thumbnails)?
   • Should rollbacks be supported for failed bulk operations (e.g., AssetMetadataBulkEventDispatcher)?

Integration Approach

Stack Fit

Migration Path

1. Phase 1: Dependency Upgrade

   • Upgrade Symfony to 7.3+ and PHP to 8.3+.
   • Update Doctrine, Messenger, and Monolog to compatible versions.
   • Test with a staging environment using Docker (anzusystems/php image).

2. Phase 2: Database Schema Migration

   • Backup existing DB before applying schema changes.
   • Run Doctrine migrations for new entities (Asset, AssetFile, LicenceGroup, etc.).
   • Index existing data for Elasticsearch (use --since flag for incremental reindexing).

3. Phase 3: Core Integration

   • Install the bundle via Composer:

     composer require anzusystems/core-dam-bundle
     

   • Configure environment variables (e.g., DB_CORE_DAM_BUNDLE_*, GOOGLE_PUBSUB_SA_KEY).
   • Set up Messenger transports (e.g., Redis, AMQP) and workers:

     php bin/console messenger:consume async -vv