Cleaner Bundle Laravel Package

Product Decisions This Supports

• Data Retention & Compliance: Enables automated cleanup of stale data (e.g., logs, queues, or user sessions) to meet GDPR, CCPA, or internal retention policies, reducing legal/operational risk.
• Cost Optimization: Reduces database storage costs by purging obsolete records (e.g., old transactions, temporary files) without manual intervention.
• Performance Scaling: Mitigates bloat in databases/filesystems that degrade query speeds or increase backup times, critical for high-growth applications.
• Roadmap Efficiency: Accelerates feature development by offloading cleanup logic to a reusable, configurable bundle (vs. custom scripts).
• Build vs. Buy: Favors "buy" for teams lacking time/resources to build a robust, auditable cleanup system from scratch.
• Use Cases:
  • E-commerce: Clear abandoned carts, old orders, or inventory logs.
  • SaaS: Purge deleted user data or expired sessions.
  • Analytics: Archive legacy event logs while preserving recent data.

When to Consider This Package

• Adopt if:

  • Your Symfony/Laravel app stores data with explicit retention windows (e.g., "delete records older than 30 days").
  • You need multi-table/database cleanup (e.g., queues, logs, temp tables) with configurable queries.
  • Your team prioritizes maintainability over custom scripts (e.g., cron jobs, one-off SQL).
  • You require transactional safety (optional) for critical data deletion.
  • Your infrastructure lacks dedicated DevOps for manual cleanup processes.

• Look elsewhere if:

  • You need real-time cleanup (this is batch-oriented; use triggers/events instead).
  • Your cleanup logic requires complex business rules (e.g., soft deletes, user approvals).
  • You’re using non-Symfony/Laravel stacks (e.g., Node.js, Django).
  • The package’s last release (2020) is a dealbreaker for your team (consider forking or alternatives like spatie/laravel-schedule).
  • You need GUI management (this is CLI/config-driven; pair with tools like Adminer/PHPMyAdmin if needed).

How to Pitch It (Stakeholders)

For Executives: "This bundle automates the cleanup of stale data—like old logs, abandoned carts, or expired sessions—saving storage costs and reducing compliance risks. For example, it could cut our database size by 30% with zero manual effort. It’s a low-risk, high-reward way to optimize infrastructure without hiring additional engineers."

For Engineering: *"Leverage this to replace ad-hoc SQL scripts or cron jobs with a configurable, transaction-safe cleanup system. Key benefits:

• Symfony-native: Integrates seamlessly with existing bundles.
• Flexible: Supports multi-table deletes with custom queries (e.g., DELETE FROM orders WHERE status = 'cancelled' AND created_at < NOW() - INTERVAL '90 days').
• Scalable: Handles large datasets efficiently (batch processing under the hood).
• Maintainable: Centralized config vs. scattered cleanup logic. Tradeoff: Last updated in 2020, but the core logic is stable. We’d need to vet forks or backport fixes if critical."*

For Developers: *"Drop this into composer.json, configure YAML rules, and run php bin/console lamoda:cleaner:run. No PHP code needed—just define:

lamoda_cleaner:
    db:
        queue:
            query: DELETE FROM failed_jobs WHERE created_at < NOW() - INTERVAL '14 days'

Works for PostgreSQL/MySQL. Want to add S3 cleanup? Extend the bundle or pair with league/flysystem."*