Apa iku Proxy pattern?

Question

Accepted Answer

**Proxy** pattern nyediakne **placeholder utawa surrogate** kanggo obyek liya kanggo ngontrol akses menyang obyek kasebut. Proxy duwe interface sing sama karo obyek asli nanging nambah behavior — kaya lazy loading, kontrol akses, caching, utawa logging — sadurunge delegasi menyang obyek kasebut.

## Apa sing ditindakne dening Proxy pattern

```text
PROXY → an object that STANDS IN for another, controlling access to it:
  → same interface as the real object (clients use it transparently)
  → adds behavior BEFORE/AROUND delegating to the real object
  → controls WHEN and HOW the real object is accessed
→ "a stand-in that adds control/behavior"
```

## Jenis-jenis proxy

```text
VIRTUAL proxy → LAZY initialization → create/load the real object only when needed
  (e.g. defer loading a heavy resource until first use)
PROTECTION proxy → ACCESS CONTROL → check permissions before allowing access
CACHING proxy → cache results → return cached data instead of re-fetching/recomputing
REMOTE proxy → represent an object in another location (network/remote calls hidden)
LOGGING/smart proxy → add logging, reference counting, etc. around access
```

## Panggunaan lan conto

```js
// a caching proxy wraps a service, caching results
class CachingProxy {
  constructor(service) { this.service = service; this.cache = {}; }
  fetch(id) {
    if (!this.cache[id]) this.cache[id] = this.service.fetch(id);  // cache misses
    return this.cache[id];   // serve from cache otherwise
  }
}
```

```text
USES → ORMs (lazy-loading entities), API clients (caching/retry), JS Proxy object,
  access control, virtual proxies for heavy objects, remote service proxies
```

## Mengapa iku penting

Nemahke Proxy pattern iku berharga amarga iku **structural pattern sing migunani** kanggo ngontrol akses menyang obyek-obyek, kanthi aplikasi praktis, dadi iku relevan banget kanggo pengetahuan desain.

Proxy pattern nyediakne surrogate kanthi interface sing sama karo obyek asli, nambah behavior sadurunge delegasi menyang obyek kasebut — ngontrol kapan lan paorie obyek asli diakses.

Nemahke apa sing ditindakne (stand-in sing nambah kontrol utawa behavior dene transparantly mewakili obyek asli) iku pengetahuan inti.

Nemahke **jenis-jenis proxy** iku berharga amarga saben jenis ngatasi kabutuhan nyata: **virtual proxies** (lazy initialization — nundha pembuatan utawa loading sumber daya berat nganti diperlukan, penting kanggo performance), **protection proxies** (kontrol akses — ngecek ijin sadurunge ngidhinke akses), **caching proxies** (nyimpen hasil kanggo nyegah re-fetching utawa recomputing — optimasi umum), **remote proxies** (mewakili obyek ing lokasi liyane, ndhelikne network calls), lan logging/smart proxies.

Iku nutupi cross-cutting concerns penting (lazy loading, kontrol akses, caching, remote access) sing diterapne transparantly.

Nemahke **panggunaan** — ORMs (lazy-loading entities, aplikasi nyata sing paling umum), API clients (caching lan retry), JavaScript Proxy object, kontrol akses, lan remote service proxies — nerangne aplikabilitas praktisne.

Proxy pattern nampak ing framework nyata (ORMs lazy-load liwat proxies, JS duwe Proxy built-in) lan iku cara sing bersih kanggo nambah kontrol akses, caching, utawa lazy loading transparantly sekiling obyek.

Kamrangan Proxy pattern iku structural pattern sing migunani kanggo ngontrol akses menyang obyek-obyek (lazy loading, kontrol akses, caching, remote access) kanthi aplikasi nyata (ORMs, API clients, JS Proxy), lan nemahke apa sing ditindakne lan jenis-jenise iku relevan kanggo kabutuhan umum kasebut, dadi nemahke Proxy pattern iku pengetahuan desain sing berharga lan praktis — pattern migunani kanggo ngontrol akses obyek transparantly (lazy loading, caching, kontrol akses), nampak ing framework nyata kaya ORMs, lan pengetahuan desain penting kanggo nambah cross-cutting behavior sekiling akses obyek kanthi bersih.