Implement Redis caching, queues, pub/sub for Laravel apps.
npx skills add https://github.com/bipinks/ghost-office --skill redis-patterns-bipinks
Please help me install this Agent Skill. Skill: redis-patterns Source: https://github.com/bipinks/ghost-office/tree/main/.claude/skills/redis-patterns Command: npx skills add https://github.com/bipinks/ghost-office --skill redis-patterns-bipinks
This Skill provides a consolidated set of Redis patterns for building scalable, high-performance applications, covering caching strategies, queue management, pub/sub, rate limiting, and multi-tenant patterns.
Start by selecting a caching pattern (cache-aside, write-through, or write-behind) and implement it with Redis in your current Laravel project.
High-intent search queries and answers about installing and using this skill.
Redis caching strategies in Laravel involve implementing cache-aside, write-through, or write-behind patterns to ensure responsive reads and data consistency. You select a caching pattern and apply it with Redis to manage data access efficiently.
Isolating cache data in a multi-tenant app is best achieved by implementing a multi-tenant caching layer with per-branch keys and TTLs. This ensures data separation and prevents cache leakage between different tenants.
Redis pub/sub works by distributing events and notifications across subscribers in real-time. It enables event broadcasting across tenants, allowing services to push notifications efficiently without polling the database.
Yes, you can use Redis for queue management to handle task queues, retries, and batch processing. Redis-backed queues, when managed with Horizon, provide reliable task execution and monitoring for high-traffic services.
Best practices for Redis key naming and TTLs involve establishing clear guidance on implementation details to ensure safe Redis configuration. Proper key naming and TTLs maintain data isolation, prevent stale data, and optimize memory usage.
You should use write-behind caching instead of cache-aside when you need to handle high-write throughput by asynchronously updating the data store. Cache-aside is better suited for responsive reads where data consistency is managed on demand.
anilcancakirOrchestrates Horizon, Octane, Reverb, Redis, and PostgreSQL for Laravel queue, real-time, and caching workflows.
kid-sidCoordinate real-time client updates across distributed FastAPI services with Redis broadcast.
JayonLabsConfigure Laravel Echo broadcasting with Reverb, Pusher, or Ably.
an8079Optimize application performance across concurrency, database, caching, and vector retrieval layers.
