Zgw Vrijbrp Request Bundle Laravel Package

Product Decisions This Supports

• Extending Common Gateway Ecosystem: Enables rapid development of modular, plugin-based functionality for the Common Gateway (a Dutch government API gateway framework). Ideal for teams building on top of the ZGW (Zaken Gerelateerd Werken) ecosystem, which standardizes API integrations for Dutch public sector services.
• Plugin-Based Architecture: Supports a build vs. buy strategy by allowing custom plugins to replace or augment core functionality without modifying the base system. Reduces technical debt by isolating features into reusable bundles.
• Government Compliance & Interoperability: Aligns with Dutch public sector standards (e.g., BRP, DRCN) by providing a standardized way to integrate with APIs like the VrijBRP (Free Personal Records Database). Critical for municipalities, provinces, or agencies needing to comply with Dutch e-government regulations.
• Developer Velocity: Accelerates development cycles for Symfony/Laravel teams by leveraging Symfony Flex bundles. Reduces boilerplate for API integrations, authentication, and schema validation.
• Roadmap for Modularity: Justifies investing in a plugin marketplace or internal bundle repository for reusable components (e.g., authentication, validation, or domain-specific logic like address verification).
• Use Cases:
  • Custom API endpoints for local government services (e.g., permit applications, citizen portals).
  • Integration with niche Dutch public sector APIs (e.g., PDOK, BSR, or GBA).
  • A/B testing or feature flags via plugin swapping without redeploying the core system.

When to Consider This Package

• Adopt if:

  • Your team is building on the Common Gateway or ZGW ecosystem and needs to extend functionality without forking the core.
  • You require Dutch public sector API integrations (e.g., VrijBRP, DRCN) with minimal custom development.
  • You prioritize modularity and want to avoid monolithic codebases for API services.
  • Your stack includes Symfony/Laravel and you want to leverage Symfony Flex for plugin management.
  • You need admin-driven plugin installation (via the Common Gateway UI) to enable non-technical stakeholders to enable/disable features.

• Look elsewhere if:

  • You’re not using Common Gateway or the ZGW framework (this package is ecosystem-specific).
  • Your use case requires non-Symfony/PHP tech stacks (e.g., Node.js, Python).
  • You need high-performance, low-latency APIs where bundle overhead is prohibitive.
  • Your team lacks Symfony/Laravel experience—this package assumes familiarity with Symfony Flex and Composer.
  • You require enterprise-grade support (the package has no stars, minimal documentation, and no dependents as of 2025).

How to Pitch It (Stakeholders)

For Executives/Business Leaders:

"This package lets us plug in Dutch government API integrations—like the VrijBRP database—without rewriting core systems. Think of it like an app store for our API gateway: we can add features (e.g., new permit workflows) as plugins, enabling faster innovation and compliance with Dutch e-government standards. For example, a municipality could use this to quickly add a ‘citizen address verification’ feature without touching the main codebase. It also future-proofs our system by isolating features, making updates easier and reducing risk."

Key Benefits:

• Speed: Cut development time for API integrations by 30–50%.
• Compliance: Built for Dutch public sector APIs (e.g., BRP, DRCN).
• Flexibility: Enable/disable features via admin UI—no redeploys.
• Cost: Avoid custom development for common use cases.

For Engineering Teams:

*"This is a Symfony Flex bundle template for the Common Gateway ecosystem, designed to let us extend functionality via plugins. Here’s how we’d use it:

1. For new features: Build a plugin (e.g., a ‘PDOK Maps Integration’) and deploy it as a bundle. The Common Gateway UI auto-discovers it.
2. For Dutch APIs: Pre-built schemas for VrijBRP/DRCN reduce boilerplate for authentication/validation.
3. For modularity: Swap plugins without redeploying the core (great for A/B testing or feature flags).
4. For ops: Install/uninstall plugins via Composer or the admin panel—no manual config changes.

Trade-offs:

• Assumes Symfony/Laravel expertise (Symfony Flex is required).
• Minimal community support (early-stage package), but ideal if we’re deeply invested in Common Gateway.
• Best for government or public-sector use cases where ZGW standards apply."*

Next Steps:

• Evaluate if Common Gateway is the right foundation for our API strategy.
• Pilot with a non-critical plugin (e.g., a test VrijBRP integration).
• Assess effort to build an internal bundle repository for reusable plugins.