R&D Labs: Waffle-Commons (v0.1.0-beta2.1), a PHP Ecosystem that loves PSR

39 views
Skip to first unread message

Leslie Petrimaux (Chaton)

unread,
Jun 1, 2026, 10:21:01 AM (yesterday) Jun 1
to PHP Framework Interoperability Group

Hello PHP-FIG members,

I wanted to share a comprehensive, 100% open-source ecosystem that serves as a strict, production-grade implementation of multiple PSR standards, developed entirely as a solo project: Waffle-Commons (https://github.com/waffle-commons).

Waffle is built on a radical architectural invariant: concrete components must never depend on each other, only on abstract PSR interfaces and a centralized contracts layer. Across 16 standalone packages, I have successfully composed:

  • PSR-7 (HTTP Messages) & PSR-17 (Factories) via waffle-commons/http

  • PSR-15 (Middleware & Request Handlers) via waffle-commons/pipeline

  • PSR-11 (Container) via waffle-commons/container

  • PSR-14 (Event Dispatcher) via waffle-commons/event-dispatcher

  • PSR-3 (Logging) via waffle-commons/log

  • PSR-6 & PSR-16 (Caching) via waffle-commons/cache

  • PSR-18 (HTTP Client) via waffle-commons/http-client

This entire stack executes within a long-running, resident-memory environment (FrankenPHP Worker Mode). This constraints-driven runtime provided an excellent testing ground for exploring how stateful vs stateless PSR implementations behave over thousands of concurrent persistent loops, achieving a verified zero memory drift (ΔM = 0) thanks to automated container resets via a request-bound ResettableInterface loop (currently in progress for the next release).

I would be honored to share my data and architectural feedback with the PHP-FIG community regarding PSR interoperability, connection pooling, and boundary enforcement in modern resident-memory runtimes.

Best regards,

Leslie Petrimaux

Lead Architect & DevSecOps


Reply all
Reply to author
Forward
0 new messages