Sidecar Laravel Package

Product Decisions This Supports

• Serverless Microservices: Enables rapid deployment of lightweight, language-agnostic functions (Node.js, Python, Java, etc.) directly from Laravel, reducing reliance on monolithic services.
• Cost Optimization: Replaces expensive always-on servers for one-off tasks (e.g., image generation, PDF processing) with pay-per-use Lambda functions.
• Multi-Language Workflows: Bridges PHP (Laravel) with non-PHP runtimes (e.g., Node.js for frontend SSR, Python for ML inference) without HTTP overhead.
• Build vs. Buy: Avoids reinventing Lambda deployment logic or integrating third-party tools (e.g., Serverless Framework) for niche use cases.
• Roadmap Priorities:
  • Phase 1: Integrate Sidecar for non-critical, high-value tasks (e.g., media processing).
  • Phase 2: Expand to event-driven workflows (e.g., S3 triggers → Lambda via Sidecar).
  • Phase 3: Replace legacy cron jobs with Sidecar-managed Lambdas for scalability.

When to Consider This Package

Adopt Sidecar if:

• Your Laravel app needs to execute non-PHP code (e.g., Node.js for Puppeteer, Python for data processing) without managing separate servers.
• You’re on AWS Lambda and want a seamless Laravel-native way to deploy functions (no manual CLI or SDK setup).
• Your use case fits short-lived, stateless tasks (e.g., image generation, API transformations) rather than persistent services.
• You’re already using Laravel Vapor or AWS and want to extend its serverless capabilities.

Look elsewhere if:

• You need HTTP-triggered Lambdas (Sidecar requires execution from Laravel code).
• Your functions require API Gateway, databases, or caching (Sidecar focuses solely on Lambda execution).
• You’re not on AWS (Sidecar is AWS-only).
• You need long-running processes (>15 mins; Lambda has timeouts).
• Your team lacks AWS IAM permissions for Lambda deployment (Sidecar requires AWS credentials).

How to Pitch It (Stakeholders)

For Executives: "Sidecar lets us run specialized code (e.g., Node.js for screenshots, Python for AI) directly from Laravel—like serverless microservices on demand. It cuts costs by replacing always-on servers for one-off tasks and speeds up development by eliminating manual Lambda setup. Think of it as ‘cron jobs 2.0’: pay only when the task runs, and integrate it seamlessly with our existing PHP code."

For Engineers: *"This package abstracts AWS Lambda deployment into Laravel’s ecosystem. Write a PHP class, define your Lambda handler (Node/Python/Java/etc.), and deploy with php artisan sidecar:deploy. No YAML configs, no SDK boilerplate—just execute Lambdas from your routes or jobs. Ideal for:

• Media processing (e.g., dynamic OG images via Node.js + Canvas).
• Legacy system integrations (e.g., calling a Java library without a server).
• Prototyping (test a Python script without Docker). Tradeoff: AWS-only, but saves dev time vs. manual Lambda setup or third-party tools."