Laravel Sanctum personal access tokens are lightweight and generally performant, but there is a relatively easy way to make them even faster.

Giandomenico Di Salvatore

Redis

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

The post discusses an issue with Laravel Sanctum personal access tokens where updating the `last_used_at` column caused a performance bottleneck due to frequent database writes. It provides a solution by creating a custom `PersonalAccessToken` model that overrides the `save()` method to prevent unnecessary writes. The implementation steps include generating the model, modifying the `save()` method, and configuring Sanctum to use the custom model, resulting in improved performance.

Improving Laravel Sanctum Personal Access Token Performance