Drom Laravel Package

Product Decisions This Supports

• API Acceleration & Microservices Strategy: Enables rapid development of DROM (Domain-Related Object Mapping)-based APIs in Laravel, reducing boilerplate for CRUD, validation, and serialization. Aligns with a modular microservices roadmap where domain-specific APIs are decoupled from core business logic.
• Build vs. Buy: Justifies buying this package over custom development if:
  • Your team lacks bandwidth to build a reusable DROM abstraction layer.
  • You need consistent API contracts across microservices (e.g., for a headless CMS or B2B integrations).
  • You’re adopting Symfony-like bundles in Laravel (e.g., for enterprise-grade modularity).
• Use Cases:
  • Headless CMS/APIs: Auto-generate REST/GraphQL endpoints for domain models (e.g., User, Product) with minimal configuration.
  • Legacy System Modernization: Wrap legacy databases in modern APIs without rewriting business logic.
  • Multi-Tenant SaaS: Dynamically scaffold tenant-specific APIs with shared DROM rules.
  • Event-Driven Architectures: Use DROM to validate/transform payloads for Kafka/RabbitMQ consumers.
• Roadmap Enabler:
  • Phase 1: Pilot for 1–2 high-priority APIs to validate ROI.
  • Phase 2: Extend to internal tools (e.g., admin panels) to reduce frontend-backend coupling.
  • Phase 3: Integrate with Laravel Scout or GraphQL for search/filtering capabilities.

When to Consider This Package

• Adopt if:
  • Your team uses Laravel 10+ with PHP 8.4+ and needs Symfony-like modularity.
  • You’re building domain-centric APIs (e.g., Order, Inventory) with repetitive CRUD logic.
  • You prioritize developer velocity over customization (e.g., 80% of use cases fit the default DROM patterns).
  • Your stack includes baks-dev/core (or you’re willing to adopt it for dependency consistency).
• Look elsewhere if:
  • You need GraphQL-native features (consider rebing/graphql-laravel or spatie/laravel-graphql).
  • Your APIs require complex event sourcing (evaluate spatie/laravel-event-sourcing).
  • You’re constrained by low PHP version support (requires 8.4+).
  • Your team lacks Symfony/Bundle experience (steep learning curve for custom DROM rules).
  • You need real-time features (WebSockets; consider beyondcode/laravel-websockets).
  • The package’s lack of stars/community is a risk (mitigate with internal testing).

How to Pitch It (Stakeholders)

For Executives: "Drom Api lets us ship domain-specific APIs 30–50% faster by automating CRUD, validation, and serialization—reducing backend dev time for projects like [X Initiative]. It’s a Symfony-inspired module for Laravel, ideal if we’re building microservices or modernizing legacy systems. The MIT license avoids vendor lock-in, and the PHP 8.4+ requirement aligns with our tech stack. We’ll pilot it for [Y API] to prove ROI before scaling."

For Engineering: *"Drom solves the ‘I need a REST endpoint for this model’ problem with minimal code. Key benefits:

• Auto-generates API routes, controllers, and DTOs for Eloquent models (configurable via annotations).
• Integrates with Laravel’s ecosystem (e.g., works with Sanctum for auth, Scout for search).
• Extensible: Override DROM rules for complex cases (e.g., nested resources).
• Tested: Includes PHPUnit group for validation. Tradeoff: Requires PHP 8.4+ and assumes you’re okay with Symfony-like patterns. Let’s start with [Z use case] to validate."*