Graphql Mapper Bundle Laravel Package

Product Decisions This Supports

• Legacy System Modernization: Accelerate migration of older Symfony 2.x/3.x APIs to GraphQL without a full rewrite, reducing technical debt.
• Rapid API Prototyping: Quickly expose existing Doctrine entities as GraphQL endpoints for frontend teams (e.g., React/Vue) without building custom resolvers.
• Internal Tooling: Enable self-service data access for non-engineering teams (e.g., marketing, analytics) via GraphQL queries.
• Build vs. Buy: Justify using this over building a custom GraphQL layer if:
  • The team lacks GraphQL expertise.
  • The schema is simple (CRUD operations on existing entities).
  • The project timeline is tight (last release in 2016, but may suffice for basic needs).
• Roadmap: Phase 1 of a GraphQL strategy—start with this bundle, then migrate to a modern solution (e.g., Symfony’s api-platform/graphql) later.

When to Consider This Package

• Avoid if:
  • Your project uses Symfony 4+ (this bundle targets Symfony 2/3).
  • You need complex GraphQL features (subscriptions, custom directives, batch loading).
  • Your team requires long-term maintenance (last release in 2016; no active development).
  • You’re building a public API (risk of security/performance gaps in an unmaintained package).
  • You need performance optimizations (e.g., DataLoader, persistent queries).
• Look elsewhere if:
  • You’re using PHP 8+ (compatibility issues likely).
  • Your schema requires dynamic field resolution or runtime schema stitching.
  • You need integration with modern tools (e.g., GraphQL Playground, Apollo Client).
  • Your use case involves real-time updates (WebSockets/subscriptions).

How to Pitch It (Stakeholders)

For Executives: "This bundle lets us expose our existing Symfony backend as a GraphQL API with minimal dev effort—think of it as a ‘bridge’ to modernize our APIs without a full rewrite. It’s ideal for internal tools or quick frontend integration, but we’ll phase it out once we adopt a more robust GraphQL solution. Low risk, fast ROI for early adopters like [Team X]."

For Engineering: *"Pros:

• Zero resolver code: Maps Doctrine entities to GraphQL types via YAML config.
• Symfony-native: Integrates with existing security, validation, and routing.
• Quick setup: Schema-as-code in YAML (no PHP boilerplate).

Cons:

• Outdated: Last release in 2016 (but works for basic CRUD).
• No active maintenance: We’d need to patch any issues ourselves.
• Limited features: No subscriptions, custom directives, or advanced performance tools.

Recommendation: Use this for [specific use case, e.g., ‘the admin dashboard rewrite’] as a stopgap. Plan to migrate to api-platform/graphql or webonyx/graphql-php within [X months]."*

For Frontend Teams: *"This gives you GraphQL endpoints for [specific entities, e.g., ‘User, Product, Order’] with no backend changes. You’ll get predictable queries like:

query {
  users { id name email }
}

Just point your Apollo/Relay client to /graphql—we’ll handle the rest."*