Pbjc Laravel Package

Technical Evaluation

• Architecture fit: gdbots/pbjc is a build-time schema compiler, not a Laravel runtime package. It is best treated as a development/CI tool that converts PBJ schemas into JSON Schema, PHP, JS, and related artifacts. In a Laravel codebase it could generate DTOs/value objects, validation schemas, or frontend contracts, but it should not sit in the request path or be loaded as a normal application dependency.
• Integration feasibility: Low to moderate. Composer installation is likely straightforward, but the package is unmaintained since 2019, has zero stars and zero dependents, and may not support current PHP/Laravel versions without patches. Generated PHP may not follow Laravel conventions and would need review before committing to app/ or domain namespaces.
• Technical risk: High. Key risks include abandoned maintenance, unknown compatibility with modern PHP, dependency drift, no security patching, limited community support, and reliance on a niche PBJ schema language. Generated code can also create long-term ownership burden because the team must understand and maintain the compiler output even if the generator is replaced.
• Key questions: Is PBJ already the source of truth for schemas? Are generated PHP and JSON Schema artifacts acceptable to own? Which PHP/Laravel versions must be supported? Can the team fork and patch the compiler if needed? Does generated output align with existing domain models, validation, and API contracts? Is the license and generated-code provenance acceptable?

Integration Approach

• Stack fit: Use only as a dev/build dependency in Laravel projects that already standardize on PBJ schemas. Generated PHP can support application DTOs or domain transfer objects; generated JSON Schema can support API contract validation; generated JS can support frontend/backend schema alignment. It is not a fit for typical Laravel applications without an existing PBJ schema workflow.
• Migration path: Start with a bounded pilot domain. Generate artifacts into an isolated namespace or generated/ directory, review diffs manually, commit generated code, and add contract tests. Avoid mixing generated and handwritten classes until ownership and conventions are clear.
• Compatibility: Pin PHP and Composer versions, run the compiler in a controlled container or CI job, and validate output against the target Laravel version before adoption. Assume patches or a fork may be required for modern PHP. Keep the generator isolated so it can be replaced without rewriting application code.
• Sequencing: Inventory existing schemas and generated artifacts; run a small proof of concept; validate PHP syntax, runtime behavior, JSON Schema compatibility, and frontend output; decide whether to vendor/fork; add CI generation and drift checks; then expand domain by domain.

Operational Impact

• Maintenance: High if the compiler becomes part of the delivery pipeline. The package is effectively unmaintained, so the team should expect to own upgrades, bug fixes, and PHP compatibility work. Generated artifacts also require review and version control discipline.
• Support: Very limited external support. With zero stars, zero dependents, and no recent releases, there is little community knowledge, documentation, or ecosystem safety net. Internal documentation and ownership are mandatory.
• Scaling: The compiler itself is build-time and should scale acceptably for normal schema counts. Runtime scaling depends on generated code quality and how generated DTOs/validation are used. Large schema sets may expose slow generation, noisy diffs, or complex CI artifacts.
• Failure modes: Common failures include generator incompatibility with current PHP, stale generated code, schema feature gaps, inconsistent generated output across environments, dependency conflicts, and silent contract drift between PHP, JSON Schema, and JS artifacts. CI drift checks and contract tests are essential.
• Ramp-up: Moderate to high. Engineers need PBJ schema familiarity, code generation workflow knowledge, and enough understanding of the compiler internals to patch or replace it. For a Laravel team without existing PBJ usage, the ramp-up cost likely exceeds the near-term value.