Fs Laravel Package

Product Decisions This Supports

• Decentralized/Offline-First Queues: Enables local message persistence for applications requiring queue functionality without external dependencies (e.g., microservices in air-gapped environments, CLI jobs, or batch processing).
• Hybrid Queue Architectures: Complements cloud-based queues (e.g., RabbitMQ, AWS SQS) by providing a fallback filesystem transport for critical workflows during outages or network partitions.
• Cost Optimization: Reduces reliance on managed queue services for low-volume or internal workflows (e.g., log processing, report generation).
• Legacy System Integration: Bridges older PHP/Laravel systems lacking native queue support (e.g., Laravel <5.5) with minimal refactoring.
• Roadmap Flexibility: Allows teams to prototype queue-based features (e.g., async notifications, background jobs) before committing to a cloud provider.
• Build vs. Buy: Justifies "buy" for teams needing a lightweight, self-hosted solution over building custom file-based queue logic.

When to Consider This Package

• Avoid When:
  • High Throughput Needs: Filesystem I/O is slower than in-memory or network-based transports (e.g., Redis, RabbitMQ). Avoid for >10K messages/sec.
  • Distributed Systems: No built-in clustering or failover; single-node only. Not suitable for multi-server deployments.
  • Advanced Features: Lacks retries, dead-letter queues, or priority queues out of the box (requires Enqueue’s core library).
  • Modern Laravel Ecosystem: Laravel’s native database/Redis queues are more integrated and maintained. Only consider if filesystem is a hard requirement (e.g., Docker volumes, ephemeral storage).
  • Active Maintenance: Last release in 2017; evaluate risk for long-term projects. Prefer alternatives like spatie/laravel-queue-filesystem for Laravel-specific updates.
• Consider When:
  • Local Development/Testing: Simulate queue behavior without external services (e.g., Docker containers, CI pipelines).
  • Edge Cases: Applications needing queues but blocked by firewall restrictions or air-gapped systems.
  • Prototyping: Quick validation of queue patterns before investing in cloud providers.
  • Legacy Codebases: Migrating from custom file-based queues to a standardized solution.

How to Pitch It (Stakeholders)

For Executives:

"This package lets us run background jobs locally using files instead of cloud queues, cutting costs for low-volume workflows (e.g., report generation) and eliminating dependency on external services. Ideal for offline systems or prototypes—think of it as a ‘queue Lite’ for scenarios where simplicity and self-hosting outweigh performance. Risk is low for short-term use, but we’d pair it with a cloud queue for production at scale."

For Engineering:

*"The enqueue/fs package implements the Queue Interop spec, so it’s a drop-in replacement for other Enqueue transports (e.g., RabbitMQ). It stores messages as files in a directory, which is useful for:

• Local dev/testing: No RabbitMQ/Redis setup needed.
• Fallback queues: Sync messages to a cloud queue and persist locally for resilience.
• Legacy systems: Add queue support to older PHP apps with minimal changes.

Tradeoffs:

• Slower: Filesystem I/O is ~100x slower than Redis for high-throughput jobs.
• No clustering: Only works on a single machine.
• Stale: Last updated in 2017; use with caution in production.

Recommendation: Use for non-critical paths or pair with a primary cloud queue. For Laravel, consider spatie/laravel-queue-filesystem for tighter integration."*