Product Decisions This Supports
- Build vs. buy/use OSS: Avoid building custom Laravel event-delivery plumbing for audit signals, activity notifications, integration callbacks, or operational events. The package provides fail-silent immediate delivery, explicit async queue mode, force delivery, stable identifiers, payload redaction, transaction-aware enqueueing, and capped retries.
- Roadmap sequencing: Teams can ship event-driven features earlier instead of spending roadmap capacity on delivery infrastructure, idempotency identifiers, retry policy, privacy controls, and health reporting.
- Feature design: Four event levels support severity-based routing and product decisions about which events are best-effort versus force-delivered. Stable event identifiers support deduplication and downstream reconciliation.
- Reliability and compliance: Transaction-aware enqueue reduces phantom events; bounded/redacted payloads reduce PII exposure; the 24-hour transient retry cap bounds delivery latency and queue growth.
- Operational readiness: The authenticated
/psst-health endpoint with scalar metrics, caching, and last-good values gives PM/ops a simple signal for adoption health and incident triage.
- Use cases to evaluate: domain/operational event emission, audit-style activity records, user/system notifications, integration handoffs, and internal observability events. It is not a substitute for a full analytics warehouse, cross-language message bus, or workflow engine.
When to Consider This Package
Consider it when:
- The product is on Laravel 12/13 and PHP 8.3+.
- You need Laravel-native event delivery with fail-silent behavior for non-critical events and force delivery for critical ones.
- You want async queue delivery without designing queue contracts, retry caps, and transaction-aware enqueueing from scratch.
- Payloads may contain sensitive data and you need bounded/redacted payload handling.
- You need stable event identifiers for downstream deduplication or reconciliation.
- You want a low-effort operational health check via
/psst-health and are comfortable with an authenticated scalar-metrics endpoint.
- You value MIT licensing, auto-discovery, and publishable configuration for fast Laravel adoption.
Look elsewhere when:
- The stack is older than Laravel 12 or PHP 8.3.
- You require exactly-once delivery, strict ordering, cross-language consumers, long-term event retention, or high-volume streaming.
- You need a mature vendor SLA, commercial support, or a long-established API surface; v1.0.0 is an initial standalone release and should be piloted.
- You need complex workflow orchestration, analytics querying, or warehouse-grade event storage.
- Fail-silent delivery is unacceptable for business-critical events without additional monitoring and force-delivery design.
How to Pitch It (Stakeholders)
Executives: This is a low-cost, MIT-licensed Laravel package that reduces custom plumbing for reliable product and operational events. It brings privacy controls, retry limits, transaction awareness, and a health endpoint, which lowers delivery risk and speeds time-to-market for event-driven features. Approve a contained pilot on Laravel 12/13/PHP 8.3+ before broad rollout.
Engineering: Adoption is Laravel-native through provider/facade auto-discovery and publishable config. Use immediate fail-silent delivery for best-effort events, async queue mode for throughput/latency isolation, and force delivery only for must-not-drop cases. Validate redaction, idempotency keys, queue capacity, retry behavior, and /psst-health metrics in staging. Treat v1.0.0 as an initial release: pin the version and define an upgrade/rollback plan.
Product/ops: The package supports event taxonomy and severity decisions without building delivery infrastructure. Define which events are best-effort versus force-delivered, monitor the health endpoint, and confirm that fail-silent behavior aligns with user-facing expectations. Decision: pilot with clear success criteria around delivery reliability, payload safety, and operational visibility.