Why I Built a Redis-Backed Alternative to Spatie Permissions
php
dev.to
If you've worked with Laravel for more than a week, you've probably installed spatie/laravel-permission. It's the default answer to "how do I add roles and permissions to my app?" -- and for good reason. It's well-maintained, well-documented, and battle-tested. So why did I build laravel-permissions-redis? Because at scale, the database becomes the bottleneck. The problem I kept hitting I was building a multi-tenant SaaS with a Laravel API serving ~200 requests/second. Each request