Zgw To Zds Bundle Laravel Package

Product Decisions This Supports

• Modular Architecture for Government APIs: Enables rapid extension of the Common Gateway (a Dutch government API platform) via Symfony Flex bundles, reducing dependency on core team for new features.
• Plugin Economy for Public Services: Supports a "build vs. buy" strategy—teams can develop custom plugins (e.g., for pet store APIs, healthcare, or municipal services) without modifying the monolithic core.
• Roadmap for Decoupled Microservices: Aligns with a phased migration from monolithic to modular API gateways, where plugins handle domain-specific logic (e.g., ZGW-to-ZDS data transformations).
• Use Cases:
  • Regional Customizations: Municipalities extending gateway functionality (e.g., local tax APIs).
  • Legacy System Integration: Plugins to bridge older ZGW (Zaken Gateway) systems with modern ZDS (Dossier Service) standards.
  • Experimental Features: Sandboxing new APIs (e.g., PetStoreBundle as a proof-of-concept) before core integration.

When to Consider This Package

• Adopt if:

  • Your team maintains or extends the Common Gateway ecosystem (Dutch public sector APIs).
  • You need to develop or distribute plugins for Symfony-based API gateways with minimal core changes.
  • Your roadmap includes modularizing monolithic API logic (e.g., separating ZGW/ZDS transformations into plugins).
  • You require admin UI-driven plugin installation (via Common Gateway’s Plugins tab) to reduce manual DevOps overhead.

• Look Elsewhere if:

  • Your project isn’t tied to the Common Gateway or Symfony Flex bundles.
  • You need high-performance plugins (this is a template; performance depends on implementation).
  • Your use case requires non-PHP languages or frameworks (e.g., Node.js, Go).
  • You lack Composer/Docker infrastructure for plugin deployment.

How to Pitch It (Stakeholders)

For Executives: "This package lets us extend the Common Gateway’s API capabilities without touching the core system, reducing technical debt and accelerating feature delivery. For example, municipalities can now add local tax APIs as plugins—deployed via a simple UI—while the central team focuses on stability. It’s a ‘build vs. buy’ enabler: teams can develop plugins internally or source them from a future marketplace, cutting time-to-market for public services."

For Engineering: *"This is a Symfony Flex bundle template for the Common Gateway, designed for:

1. Rapid Plugin Development: Use the PetStoreBundle as a blueprint to create domain-specific plugins (e.g., ZGW-to-ZDS data converters).
2. Zero-Core Modifications: Plugins auto-discover and install via Composer or the admin UI (common-gateway:install command).
3. Scalable Architecture: Ideal for migrating monolithic logic (e.g., Zaken Gateway integrations) into modular plugins. Tradeoff: Early-stage (0 stars, but actively maintained by Common Gateway). Start with the PetStoreBundle to validate the pattern before building critical plugins."*