Cache tags in Laravel allow you to group and invalidate related cache entries. 1. Tags are labels attached to cached items, enabling targeted invalidation. 2. They are useful for user-specific data, multi-tenant apps, and CMS content updates. 3. Supported drivers include Redis and database; file or array drivers do not support tagging. 4. Use Cache::tags() to store, retrieve, and flush tagged entries. 5. Flushing a tag marks entries as stale but does not remove them immediately. 6. Avoid inconsistent tag names and overuse to maintain performance.
When you're working with caching in Laravel, one of the more powerful tools available is cache tagging. It allows you to group related cache entries together and invalidate them all at once — which can be super handy when you need to clear specific cached data without wiping out your entire cache.

What Are Cache Tags and Why Use Them?
Cache tags are like labels you attach to cached items. They don’t affect how data is stored, but they give you a way to organize and target groups of cached values. This becomes really useful when, for example, multiple cache entries depend on the same underlying data — like user-related info or settings for a particular tenant in a multi-tenant app.

Instead of trying to track every single key that might be affected by a change, you just tag them all with something like 'user_123'
and then flush all entries under that tag when needed.
Note: Cache tagging only works with certain cache drivers — Redis and database drivers support it, but file or array drivers do not.
![]()
How to Use Cache Tags in Laravel
Using cache tags is pretty straightforward. You use the tags()
method when interacting with the cache facade:
// Storing a value with tags Cache::tags(['user_123', 'settings'])->put('user_profile', $profileData, 60); // Retrieving a tagged value $profile = Cache::tags(['user_123'])->get('user_profile'); // Invalidating all entries tagged with 'user_123' Cache::tags(['user_123'])->flush();
Here’s what this looks like in practice:
- You store a user’s profile, dashboard stats, and settings under the same tag.
- When the user updates their email, you just flush the
user_123
tag, and all related cached data gets cleared automatically.
This keeps things clean and avoids stale data showing up because one cache key was missed.
Common Scenarios Where Tagging Helps
Some typical situations where cache tags shine include:
-
User-specific data: Each user has a unique tag like
'user_{id}'
. Any time the user changes their info, you flush that tag. -
Tenant-level caching in SaaS apps: If you’re building a multi-tenant app, you might tag everything related to a tenant with
'tenant_{id}'
. -
Content updates in CMS: For example, if an article is updated, you can flush all cache entries tagged with
'article_{id}'
, including page fragments, API responses, etc.
Just keep in mind that while tags make invalidation easier, overusing them (or using too many overlapping tags) can slow things down — especially with large datasets.
A Few Gotchas to Watch For
There are a few quirks and limitations to be aware of:
- As mentioned earlier, not all cache drivers support tags — so double-check your
.env
config. - Flushing a tag doesn’t remove the actual keys immediately; it marks the tag as "stale" and old entries will get cleaned up when accessed again or during garbage collection.
- Be careful with dynamic tag names — if you accidentally generate slightly different tags each time (like
'user_123 '
with a space), you’ll end up with orphaned cache entries.
One thing I’ve found helpful is to centralize tag naming logic in a service class or helper function. That way, you avoid inconsistencies and make it easier to update later.
That’s basically how cache tags work in Laravel. It's not complicated, but it does require some planning around how you structure your tags and when you choose to flush them.
The above is the detailed content of Using Cache Tags for Invalidating Cache Entries in Laravel. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

ToworkeffectivelywithpivottablesinLaravel,firstaccesspivotdatausingwithPivot()orwithTimestamps(),thenupdateentrieswithupdateExistingPivot(),managerelationshipsviadetach()andsync(),andusecustompivotmodelswhenneeded.1.UsewithPivot()toincludespecificcol

Laravelprovidesacleanandflexiblewaytosendnotificationsviamultiplechannelslikeemail,SMS,in-appalerts,andpushnotifications.Youdefinenotificationchannelsinthevia()methodofanotificationclass,andimplementspecificmethodsliketoMail(),toDatabase(),ortoVonage

Dependency injection automatically handles class dependencies through service containers in Laravel without manual new objects. Its core is constructor injection and method injection, such as automatically passing in the Request instance in the controller. Laravel parses dependencies through type prompts and recursively creates the required objects. The binding interface and implementation can be used by the service provider to use the bind method, or singleton to bind a singleton. When using it, you need to ensure type prompts, avoid constructor complications, use context bindings with caution, and understand automatic parsing rules. Mastering these can improve code flexibility and maintenance.

Laravel performance optimization can improve application efficiency through four core directions. 1. Use the cache mechanism to reduce duplicate queries, store infrequently changing data through Cache::remember() and other methods to reduce database access frequency; 2. Optimize database from the model to query statements, avoid N 1 queries, specifying field queries, adding indexes, paging processing and reading and writing separation, and reduce bottlenecks; 3. Use time-consuming operations such as email sending and file exporting to queue asynchronous processing, use Supervisor to manage workers and set up retry mechanisms; 4. Use middleware and service providers reasonably to avoid complex logic and unnecessary initialization code, and delay loading of services to improve startup efficiency.

Methods to manage database state in Laravel tests include using RefreshDatabase, selective seeding of data, careful use of transactions, and manual cleaning if necessary. 1. Use RefreshDatabasetrait to automatically migrate the database structure to ensure that each test is based on a clean database; 2. Use specific seeds to fill the necessary data and generate dynamic data in combination with the model factory; 3. Use DatabaseTransactionstrait to roll back the test changes, but pay attention to its limitations; 4. Manually truncate the table or reseed the database when it cannot be automatically cleaned. These methods are flexibly selected according to the type of test and environment to ensure the reliability and efficiency of the test.

LaravelSanctum is suitable for simple, lightweight API certifications such as SPA or mobile applications, while Passport is suitable for scenarios where full OAuth2 functionality is required. 1. Sanctum provides token-based authentication, suitable for first-party clients; 2. Passport supports complex processes such as authorization codes and client credentials, suitable for third-party developers to access; 3. Sanctum installation and configuration are simpler and maintenance costs are low; 4. Passport functions are comprehensive but configuration is complex, suitable for platforms that require fine permission control. When selecting, you should determine whether the OAuth2 feature is required based on the project requirements.

Laravel simplifies database transaction processing with built-in support. 1. Use the DB::transaction() method to automatically commit or rollback operations to ensure data integrity; 2. Support nested transactions and implement them through savepoints, but it is usually recommended to use a single transaction wrapper to avoid complexity; 3. Provide manual control methods such as beginTransaction(), commit() and rollBack(), suitable for scenarios that require more flexible processing; 4. Best practices include keeping transactions short, only using them when necessary, testing failures, and recording rollback information. Rationally choosing transaction management methods can help improve application reliability and performance.

The core of handling HTTP requests and responses in Laravel is to master the acquisition of request data, response return and file upload. 1. When receiving request data, you can inject the Request instance through type prompts and use input() or magic methods to obtain fields, and combine validate() or form request classes for verification; 2. Return response supports strings, views, JSON, responses with status codes and headers and redirect operations; 3. When processing file uploads, you need to use the file() method and store() to store files. Before uploading, you should verify the file type and size, and the storage path can be saved to the database.
