Apa sistem cache sing disediaken Laravel?

Question

Accepted Answer

Laravel menawarkan sistem **caching** sing terpadu lan ekspresif kanthi multiple backends (Redis, Memcached, file, database, array) ing baluri API tunggal. Caching nyimpen hasil sing larang supaya ora perlu dihitung maneh — iku minangka salah satuHighest-impact performance optimizations.

## Cache API

```php
use Illuminate\Support\Facades\Cache;

Cache::put('key', $value, 3600);          // store for 1 hour (seconds)
Cache::get('key');                         // retrieve (null if missing)
Cache::get('key', 'default');              // with a default
Cache::has('key');
Cache::forget('key');                      // delete (invalidate)
Cache::forever('key', $value);             // store with no expiry
```

## remember() — pola get-or-compute (paling migunani)

```php
// if cached, return it; otherwise run the closure, cache the result, and return it
$users = Cache::remember('active_users', 3600, function () {
    return User::where('active', true)->get();   // expensive query — cached for 1 hour
});
```

`Cache::remember()` minangka pola sing elegan lan umum: iku balik nilai sing cached yen ana, utawa ngetung (njalanke closure), nycache, lan balikke — ing siji panggilan. Sempurna kanggo caching asil query sing larang.

## Backends sing bisa dikonfigurasi (Redis kanggo production)

```text
config/cache.php → choose the driver:
  redis     → fast, SHARED across servers (production standard for multi-server apps)
  memcached → fast, shared
  file/database → simpler, for smaller/single-server setups
  array     → in-memory, for testing
The SAME Cache API works regardless of backend → easy to switch.
```

API sing terpadu ateges kode sing sama bisa digunakake karo backend apa wae — lan **Redis** minangka standar kanggo production (cache sing dishare menyang multiple server instances).

## Cache invalidation (bagian sing sulit)

```php
// when data changes, clear the affected cache or it serves stale data
public function updateUser($user, $data) {
    $user->update($data);
    Cache::forget('active_users');     // INVALIDATE so the next read recomputes
}
// strategies: TTL (accept brief staleness), explicit forget on writes, cache tags
Cache::tags(['users'])->flush();        // tagged invalidation (Redis/Memcached)
```

## Mengapa iku penting

Caching minangka salah satuHighest-impact performance optimizations kanggo aplikasi Laravel, lan sistem caching framework sing terpadu lan ekspresif nggawekake bisa diakses — dadi ngerti iku migunani kanggo ngbangun aplikasi sing cepet lan scalable.

Nilai inti yaiku nyegah pekerjaan mahal sing dibaleni: caching asil query database sing alon, komputasi kompleks, utawa external API calls ateges request sakulawarga dilayani kanthi cepet, drastis nyuda latency lan load.

Caching Laravel minangka elegan, khususé pola **`Cache::remember()` get-or-compute** (balik data sing cached yen ana, utawa ngetung, nycache, lan balikke ing siji panggilan sing bersih — ideal kanggo caching asil query), lan **API sing terpadu menyang backends** ateges kode sing sama bisa digunakake karo driver apa wae.

Ngerti nggunakake **Redis** kanggo production (cache sing dishare menyang multiple server instances — penting amarga cache per-server sing luwih saja ora dishare nalika scaling horizontally) minangka poin arsiitektur sing penting.

Kutuwane uga ngerti kesulitan sentral caching — **invalidation** (mbusak utawa nyegarke data sing dicache nalika data dasaran owah, liwat TTLs, explicit `forget` ing writes, utawa cache tags, kanggo nyegah nglayani data lawas) — amarga salah nglakukake iku minangka kegagalan caching klasik sing nunjukake pangguna informasi sing lawas.

Ngerti sistem caching Laravel — API, pola `remember`, pilihan backend (Redis kanggo scale), lan khususé strategi invalidation — minangka pengetahuan level senior penting kanggo ngbangun aplikasi Laravel sing performan lan scalable, amarga caching menehi keuntungan performance sing gedhe nanging mbutuhke invalidation sing teliti supaya tetep bener.