lapeeh 1.0.0

package/doc/en/DEPLOYMENT.md

@@ -0,0 +1,171 @@
+# Deployment Guide
+
+This guide will help you deploy your lapeeh application from `localhost` to a Production Server (VPS/Cloud).
+
+## Pre-Deployment Preparation
+
+Before deploying, ensure:
+
+1.  **Environment Variables**: Prepare `.env` values for production (Strong JWT Secret, etc.).
+2.  **Build**: TypeScript must be compiled to JavaScript.
+
+## Strategy 1: VPS (Ubuntu/Debian) with PM2
+
+This is the most common and cost-effective way.
+
+### 1. Setup Server
+
+Ensure Node.js and NPM are installed on the server.
+
+### 2. Clone & Install
+
+```bash
+git clone https://github.com/username/your-repo.git
+cd your-repo
+npm install --production=false # Install devDependencies for build
+```
+
+### 3. Build Application
+
+```bash
+npm run build
+```
+
+This will generate a `dist/` folder.
+
+### 4. Setup Production Config
+
+```bash
+cp .env.example .env
+nano .env # Fill with production config
+```
+
+### 5. Run with PM2
+
+lapeeh includes an automatic PM2 configuration (`ecosystem.config.js`).
+
+1.  **Install PM2 Global**:
+
+    ```bash
+    npm install -g pm2
+    ```
+
+2.  **Run Application**:
+
+    ```bash
+    pm2 start ecosystem.config.js
+    ```
+
+    This command will:
+
+    - Run the application in **Cluster** mode (using all available CPU cores).
+    - Set `NODE_ENV` to `production`.
+    - Enable auto-restart if the app crashes or memory usage exceeds 1GB.
+
+3.  **Check Status**:
+
+    ```bash
+    pm2 status
+    pm2 logs
+    ```
+
+4.  **Save Startup Config (To run on reboot)**:
+    ```bash
+    pm2 save
+    pm2 startup
+    ```
+
+### ❓ FAQ: Why Does My App Appear Multiple Times in PM2?
+
+If you run `pm2 list` and see your app name appear multiple times, **DON'T WORRY**. This is a feature, not a bug.
+
+- **Cause**: `instances: "max"` and `exec_mode: "cluster"` configuration in `ecosystem.config.js`.
+- **Function**: PM2 detects the number of CPU cores on your VPS and creates 1 worker process for each core.
+- **Benefit**: Your application becomes **Multi-Threaded**. Requests are distributed evenly across all processes, improving performance.
+
+**How to change to Single Instance (Save RAM):**
+If your server RAM is limited (e.g., 512MB/1GB), modify `ecosystem.config.js`:
+
+```javascript
+module.exports = {
+  apps: [
+    {
+      name: "my-app",
+      // ...
+      instances: 1, // Change "max" to 1
+      // ...
+    },
+  ],
+};
+```
+
+Then run `pm2 reload ecosystem.config.js`.
+
+### 7. Advanced: Running Multiple Apps (Multi-App)
+
+You can combine multiple Node.js apps in one `ecosystem.config.js`.
+
+### 8. Reverse Proxy (Nginx)
+
+Do not expose port 8000 directly. Use Nginx in front of it.
+Nginx block config:
+
+```nginx
+server {
+    server_name api.your-domain.com;
+    location / {
+        proxy_pass http://localhost:8000;
+        proxy_http_version 1.1;
+        proxy_set_header Upgrade $http_upgrade;
+        proxy_set_header Connection 'upgrade';
+        proxy_set_header Host $host;
+        proxy_cache_bypass $http_upgrade;
+    }
+}
+```
+
+## Strategy 2: Docker (Container)
+
+lapeeh includes a `Dockerfile`.
+
+**Minimal Dockerfile:**
+
+```dockerfile
+FROM node:18-alpine
+
+WORKDIR /app
+
+COPY package*.json ./
+RUN npm install
+
+COPY . .
+RUN npm run build
+
+EXPOSE 8000
+CMD ["npm", "run", "start:prod"]
+```
+
+**Deploy:**
+
+```bash
+docker build -t my-lapeeh-app .
+docker run -p 8000:8000 --env-file .env my-lapeeh-app
+```
+
+## Strategy 3: PaaS (Railway / Render / Vercel)
+
+Platforms like Railway.app are very easy as they detect `package.json`.
+
+1.  Push code to GitHub.
+2.  Connect repo on Railway/Render.
+3.  Set Environment Variables in their dashboard.
+4.  Set **Build Command**: `npm run build`.
+5.  Set **Start Command**: `npm run start:prod`.
+
+## Production Security Checklist
+
+- [ ] `NODE_ENV=production` must be set.
+- [ ] `JWT_SECRET` must be long and random.
+- [ ] Database credentials (if used) must be secure.
+- [ ] Rate Limiting active (lapeeh default is active).
+- [ ] Use HTTPS (SSL) via Nginx or Cloudflare.

package/doc/en/FAQ.md

@@ -0,0 +1,69 @@
+# Frequently Asked Questions (FAQ)
+
+Kumpulan pertanyaan umum dan solusi untuk masalah yang sering dihadapi.
+
+## Database
+
+### Q: Database apa yang didukung?
+
+**A:**
+lapeeh bersifat **Database Agnostic**. Anda bisa menggunakan PostgreSQL, MySQL, MongoDB, atau database apapun. Framework tidak membatasi pilihan database Anda. Kami menyediakan wrapper `db` generik yang bisa Anda konfigurasi sesuai kebutuhan.
+
+## Redis & Caching
+
+### Q: Saya tidak ingin pakai Redis di local, ribet installnya.
+
+**A:**
+Tenang, lapeeh otomatis mendeteksi jika Redis tidak berjalan dan akan menggunakan **In-Memory Mock** (simulasi Redis di RAM). Aplikasi tetap jalan normal tanpa error. Anda tidak perlu config apa-apa.
+
+### Q: Bagaimana cara clear cache Redis?
+
+**A:**
+Jika punya akses CLI Redis: `redis-cli FLUSHALL`.
+Atau via kode:
+
+```typescript
+import { redis } from "@/core/redis";
+await redis.flushall();
+```
+
+## Fitur & Kustomisasi
+
+### Q: Bagaimana cara handle File Upload?
+
+**A:**
+Gunakan `multer`. Framework sudah menyiapkannya di `src/routes/auth.ts` sebagai contoh (upload avatar).
+Anda bisa copy logic konfigurasi `multer` tersebut ke route lain.
+
+### Q: Bagaimana cara menambah middleware global baru?
+
+**A:**
+Buka `src/core/server.ts`. Di sana ada bagian `// Global Middlewares`. Tambahkan middleware Express Anda di situ:
+
+```typescript
+app.use(myCustomMiddleware);
+```
+
+### Q: Saya ingin mengubah port server.
+
+**A:**
+Cukup ubah variabel `PORT` di file `.env`. Defaultnya adalah `8000`.
+
+## Troubleshooting
+
+### Q: Error `EADDRINUSE: address already in use :::8000`
+
+**A:**
+Artinya port 8000 sedang dipakai program lain (atau instance lapeeh sebelumnya yang nyangkut).
+**Solusi:**
+
+1. Matikan terminal.
+2. Jalankan perintah kill (framework biasanya memberi saran commandnya saat error muncul).
+   - Windows: `taskkill /F /IM node.exe` (Hati-hati ini mematikan semua node process).
+   - Atau cari PID nya: `netstat -ano | findstr :8000`.
+
+### Q: Error `Unique constraint failed` saat seeding
+
+**A:**
+Data yang mau dimasukkan sudah ada (misal email `sa@sa.com`).
+Jalankan `npm run db:reset` untuk menghapus semua data dan mulai dari nol.

package/doc/en/FEATURES.md

@@ -0,0 +1,99 @@
+# Features & Core Concepts
+
+This document explains the key features of lapeeh Framework and how to use them in depth.
+
+## 1. Data Validation (Simple & Powerful)
+
+The framework provides a `Validator` utility inspired by expressive modern validation styles, using `zod` behind the scenes but with an API that is more string-based and readable.
+
+**Location:** `@lapeeh/utils/validator`
+
+### Basic Usage
+
+```typescript
+import { Validator } from "@lapeeh/utils/validator";
+
+export async function createProduct(req: Request, res: Response) {
+  const validator = await Validator.make(req.body, {
+    name: "required|string|min:3",
+    price: "required|number|min:1000",
+    email: "required|email|unique:user,email", // Check unique in user table email column
+    category_id: "required|exists:category,id", // Check exists in category table id column
+    photo: "required|image|max:2048", // Validate file upload (Max 2MB)
+  });
+
+  if (validator.fails()) {
+    return sendError(res, 400, "Validation failed", validator.errors());
+  }
+
+  const data = validator.validated();
+  // Continue saving process...
+}
+```
+
+### Available Rules
+
+- `required`: Must be filled.
+- `string`, `number`, `boolean`: Data type.
+- `email`: Valid email format.
+- `min:X`, `max:X`: String length or number value.
+- `unique:table,column`: Ensure value does not exist in database (Async).
+- `exists:table,column`: Ensure value exists in database (Async).
+- `image`: File must be an image (jpg, png, webp, etc).
+- `mimes:types`: File must be a specific type (e.g., `mimes:pdf,docx`).
+
+## 2. High Performance Response (Fastify-Like)
+
+For endpoints requiring high performance (e.g., large data lists), use schema-based serialization. This is much faster than standard Express `res.json`.
+
+**Location:** `@/utils/response`, `@/core/serializer`
+
+### Implementation Steps
+
+1. **Define Output Schema**
+   Match with the fields you want to show to the user.
+
+   ```typescript
+   const productSchema = {
+     type: "object",
+     properties: {
+       id: { type: "string" }, // BigInt automatically becomes string
+       name: { type: "string" },
+       price: { type: "number" },
+     },
+   };
+   ```
+
+2. **Create Serializer (Cached)**
+   Store outside the handler function so it compiles only once.
+
+   ```typescript
+   import { getSerializer, createResponseSchema } from "@/core/serializer";
+
+   const productSerializer = getSerializer(
+     "product-single",
+     createResponseSchema(productSchema)
+   );
+   ```
+
+3. **Send Response**
+
+   ```typescript
+   import { sendFastSuccess } from "@lapeeh/utils/response";
+
+   // Inside controller
+   sendFastSuccess(res, 200, productSerializer, {
+     status: "success",
+     message: "Data retrieved",
+     data: productData,
+   });
+   ```
+
+## 3. Authentication & Authorization (RBAC)
+
+The authentication system uses JWT (JSON Web Token) and supports Role-Based Access Control.
+
+### Auth Middleware
+
+- `requireAuth`: Ensures user is logged in (sends header `Authorization: Bearer <token>`).
+- `requireAdmin`: Ensures user is logged in AND has role `admin` or `super_admin`.

package/doc/en/GETTING_STARTED.md

@@ -0,0 +1,84 @@
+# Getting Started with lapeeh Framework
+
+Welcome to the official documentation for **lapeeh Framework**. This guide will help you get started with installation, configuration, and understanding the basic project structure.
+
+## System Requirements
+
+Before you begin, ensure your system meets the following requirements:
+
+- **Node.js**: Version 18.x or newer.
+- **Package Manager**: NPM (bundled with Node.js).
+
+## Installation
+
+The easiest way to start is by using the `npx` CLI generator.
+
+### 1. Create a New Project
+
+Run the following command in your terminal:
+
+```bash
+# Standard Interactive Setup
+npx lapeeh@latest init your-project-name
+```
+
+### 2. Initial Setup
+
+Once the project is created, navigate into the project directory and run the setup wizard:
+
+```bash
+cd your-project-name
+npm run first
+```
+
+This script will automatically perform the following:
+
+1.  Copy `.env.example` to `.env`.
+2.  Install all dependencies (`npm install`).
+3.  Generate a secure **JWT Secret**.
+
+### 3. Run Development Server
+
+```bash
+npm run dev
+```
+
+The server will run at `http://localhost:8000` (or the port specified in `.env`).
+
+## Directory Structure
+
+Here is the standard folder structure of lapeeh Framework:
+
+```
+my-app/
+├── bin/                  # CLI scripts for npx
+├── doc/                  # Project documentation
+├── scripts/              # Utility scripts (Generator, Compiler)
+├── src/                  # Main application source code
+│   ├── controllers/      # Business logic (Request handlers)
+│   ├── core/             # Core configuration (Redis, Server)
+│   ├── middleware/       # Express Middleware (Auth, RateLimit)
+│   ├── routes/           # API routing definitions
+│   ├── utils/            # Helper functions (Response, Validator)
+│   └── index.ts          # Application entry point
+├── .env                  # Environment variables (Secrets)
+├── package.json          # NPM Dependencies & Scripts
+└── tsconfig.json         # TypeScript Configuration
+```
+
+## Environment Configuration (.env)
+
+The `.env` file stores important configurations. Here are the key variables:
+
+```ini
+# Server
+PORT=8000
+NODE_ENV=development
+
+# Security
+JWT_SECRET="super-long-and-random-secret"
+ACCESS_TOKEN_EXPIRES_IN=3600 # 1 hour
+
+# Redis (Optional - automatically mocked if absent)
+REDIS_URL="redis://localhost:6379"
+```

package/doc/en/INTRODUCTION.md

@@ -0,0 +1,62 @@
+# Introduction to lapeeh Framework
+
+## What is lapeeh?
+
+**lapeeh** is a Backend Framework for Node.js built on top of **Express** and **TypeScript**.
+
+If you have ever used other modern frameworks, you will feel very familiar. lapeeh adopts the philosophy of ease-of-use & clean structure, while maintaining the flexibility and speed of Express.
+
+The name "lapeeh" comes from the Minang language which means "Loose" or "Free", symbolizing the freedom for developers to build applications quickly without being burdened by complicated configurations.
+
+## Why was lapeeh Created?
+
+In the Node.js ecosystem, developers often experience "Decision Fatigue":
+
+- "Which ORM to use? Prisma, TypeORM, or Drizzle?"
+- "Validation using Joi, Zod, or express-validator?"
+- "How about the folder structure? MVC? Clean Architecture?"
+- "How to handle Auth?"
+
+lapeeh answers all of that with **Opinionated Defaults**:
+
+1.  **ORM**: Prisma (Current industry standard).
+2.  **Validation**: Zod (Powerful and readable schema validation).
+3.  **Structure**: Modular MVC (Controller, Model, Route separated but cohesive).
+4.  **Auth**: Ready-to-use JWT + RBAC (Role Based Access Control).
+
+## Comparison with Other Frameworks
+
+| Feature            | Express (Raw)                 | NestJS                           | lapeeh Framework                       |
+| :----------------- | :---------------------------- | :------------------------------- | :------------------------------------- |
+| **Learning Curve** | Low (but confusing structure) | High (Angular-style, Decorators) | **Medium** (Express + Clear Structure) |
+| **Boilerplate**    | Empty                         | Very Heavy                       | **Just Right (Ready to use)**          |
+| **Type Safety**    | Manual                        | Strict                           | **Strict (Native TypeScript)**         |
+| **Dev Speed**      | Slow (manual setup)           | Medium                           | **Fast (CLI Generator)**               |
+| **Flexibility**    | Very High                     | Rigid                            | **High**                               |
+
+## "The lapeeh Way" Philosophy
+
+1.  **Developer Experience (DX) First**: CLI tools, clear error messages, and hot-reload are priorities.
+2.  **Performance by Default**: Fast JSON serialization (Fastify-style) and integrated Redis caching.
+3.  **Explicit is Better than Implicit**: No "magic" that is too dark. Your controller code is standard Express code that you understand.
+4.  **Production Ready**: Security (Helmet, Rate Limit) and Scalability (Docker, Cluster) are not afterthoughts, but built-in.
+
+## Request Lifecycle
+
+How does lapeeh handle a single request from a user?
+
+1.  **Incoming Request** (`GET /api/users`)
+2.  **Security Middleware**: Helmet (Headers), CORS, Rate Limiter.
+3.  **Global Middleware**: Request Logger, Body Parser (JSON).
+4.  **Routing**: Matching URL in `src/routes/`.
+5.  **Auth Middleware** (Optional): Check JWT token & Role.
+6.  **Validator** (Optional): Validate body/query input.
+7.  **Controller**: Main business logic executed.
+    - Call Database (via `db` adapter).
+    - Call Cache (Redis).
+8.  **Serializer**: Data formatted & sanitized (e.g., hide password).
+9.  **Response**: JSON sent back to user.
+
+---
+
+**Next:** Learn about the folder structure in [Project Structure](structure.md).

package/doc/en/PACKAGES.md

@@ -0,0 +1,63 @@
+# Referensi Package & Dependencies
+
+Dokumen ini menjelaskan fungsi dari setiap library (package) yang terinstall di lapeeh Framework, sehingga Anda mengerti kegunaan "alat-alat" yang ada di dalam kotak peralatan Anda.
+
+## Core Framework (Fondasi)
+
+Package-package ini adalah nyawa dari framework ini.
+
+| Package       | Deskripsi                         | Kenapa Kita Pakai?                                                                                      |
+| :------------ | :-------------------------------- | :------------------------------------------------------------------------------------------------------ |
+| **`express`** | Web Framework untuk Node.js.      | Standar industri, ringan, dan komunitasnya terbesar.                                                    |
+| **`dotenv`**  | Memuat variabel dari file `.env`. | Agar konfigurasi rahasia (DB password, API Key) tidak di-hardcode.                                      |
+| **`cors`**    | Cross-Origin Resource Sharing.    | Mengizinkan frontend (React/Vue) dari domain berbeda untuk mengakses API kita.                          |
+| **`helmet`**  | Middleware keamanan HTTP headers. | Melindungi aplikasi dari serangan umum (XSS, Clickjacking) dengan mengatur header HTTP secara otomatis. |
+
+## Database Driver
+
+| Package  | Description        | Why we use it?                                     |
+| :------- | :----------------- | :------------------------------------------------- |
+| **`pg`** | PostgreSQL Driver. | Native driver for connecting to Postgres database. |
+
+## Authentication & Security
+
+| Package                  | Deskripsi         | Kenapa Kita Pakai?                                    |
+| :----------------------- | :---------------- | :---------------------------------------------------- |
+| **`jsonwebtoken`**       | Implementasi JWT. | Standar token untuk autentikasi stateless (API).      |
+| **`bcryptjs`**           | Hashing password. | Mengamankan password user di database (satu arah).    |
+| **`express-rate-limit`** | Pembatas request. | Mencegah serangan DDoS ringan atau Brute Force login. |
+
+## Utilities & Helper
+
+| Package                   | Deskripsi                  | Kenapa Kita Pakai?                                                             |
+| :------------------------ | :------------------------- | :----------------------------------------------------------------------------- |
+| **`zod`**                 | Schema validation library. | Memvalidasi input user (req.body) dengan syntax yang kuat dan mudah dibaca.    |
+| **`fast-json-stringify`** | Serializer JSON cepat.     | Mengubah object ke JSON string 2x-3x lebih cepat dari `JSON.stringify` bawaan. |
+| **`uuid`**                | Generator ID unik.         | Membuat string acak unik (UUID v4).                                            |
+| **`slugify`**             | String formatter.          | Mengubah "Judul Artikel Keren" menjadi `judul-artikel-keren` (URL friendly).   |
+| **`multer`**              | Middleware upload file.    | Menangani `multipart/form-data` untuk upload gambar/dokumen.                   |
+| **`winston`**             | Logger library.            | Mencatat log aplikasi (error/info) ke file atau console dengan format rapi.    |
+
+## Realtime & Caching
+
+| Package            | Deskripsi                 | Kenapa Kita Pakai?                                                                            |
+| :----------------- | :------------------------ | :-------------------------------------------------------------------------------------------- |
+| **`socket.io`**    | Library WebSocket.        | Fitur komunikasi real-time dua arah (chat, notifikasi live).                                  |
+| **`ioredis`**      | Client Redis yang robust. | Driver terbaik untuk Redis di Node.js.                                                        |
+| **`ioredis-mock`** | Simulasi Redis di memori. | Memungkinkan development tanpa perlu install Redis server asli (sangat berguna untuk pemula). |
+
+## Development Tools (DevDependencies)
+
+Package ini hanya dipakai saat koding, tidak ikut terinstall di server production.
+
+| Package          | Deskripsi             | Fungsi                                                                         |
+| :--------------- | :-------------------- | :----------------------------------------------------------------------------- |
+| **`typescript`** | Compiler TS.          | Mengubah kode `.ts` menjadi `.js`.                                             |
+| **`nodemon`**    | Auto-restarter.       | Restart server otomatis setiap kita save file.                                 |
+| **`eslint`**     | Linter (Polisi Kode). | Mencari potensi error dan variabel yang tidak terpakai.                        |
+| **`@types/*`**   | Type Definitions.     | Provides intellisense (code suggestions) for plain JavaScript libraries.       |
+| **`tsc-alias`**  | Path resolver.        | Resolves `@/core` aliases to relative `../core` paths during production build. |
+
+---
+
+Dengan memahami daftar ini, Anda tahu persis apa yang terjadi di balik layar aplikasi Anda. Tidak ada "Bloatware", setiap package punya tujuan spesifik.

package/doc/en/PERFORMANCE.md

@@ -0,0 +1,98 @@
+# Panduan Performa & Skalabilitas lapeeh Framework
+
+Dokumen ini menjelaskan cara memaksimalkan performa aplikasi lapeeh Anda menggunakan fitur-fitur canggih seperti Fast-Serialization dan Clustering.
+
+## 1. High Performance Serialization (Fastify-Style)
+
+Express secara default menggunakan `JSON.stringify()` yang lambat karena harus memeriksa tipe data setiap field secara runtime. lapeeh mengadopsi teknik **Schema Based Serialization** (seperti Fastify) yang bisa meningkatkan throughput JSON hingga **2x-3x lipat**.
+
+### Cara Penggunaan
+
+Gunakan `sendFastSuccess` di controller Anda untuk endpoint yang membutuhkan performa tinggi (misalnya: list data yang besar).
+
+```typescript
+import { Request, Response } from "express";
+import { getSerializer, createResponseSchema } from "../core/serializer";
+import { sendFastSuccess } from "../utils/response";
+
+// 1. Definisikan Schema Output (JSON Schema Standard)
+const userSchema = {
+  type: "object",
+  properties: {
+    id: { type: "integer" },
+    name: { type: "string" },
+    email: { type: "string" },
+    // Password tidak dimasukkan, jadi otomatis tidak akan terkirim (aman!)
+  },
+};
+
+// 2. Compile Serializer (Otomatis dicache oleh framework)
+const userListSerializer = getSerializer(
+  "user-list",
+  createResponseSchema({
+    type: "array",
+    items: userSchema,
+  })
+);
+
+export async function getUsers(req: Request, res: Response) {
+  // Contoh pengambilan data dari database
+  const users = await db.users.findMany();
+
+  // 3. Kirim response super cepat
+  return sendFastSuccess(res, 200, userListSerializer, {
+    status: "success",
+    message: "Data fetched",
+    data: users,
+  });
+}
+```
+
+---
+
+## 2. Horizontal Scaling (Load Balancer & Cluster)
+
+lapeeh dirancang untuk siap di-scale secara horizontal (menambah jumlah server, bukan memperbesar spesifikasi server).
+
+### Arsitektur Cluster
+
+- **Nginx**: Bertindak sebagai Load Balancer yang membagi trafik ke server-server aplikasi.
+- **Redis**: Menyimpan Session, Rate Limit, dan Cache agar bisa diakses oleh semua server (Shared State).
+- **App Instances**: Beberapa instance aplikasi lapeeh yang berjalan paralel.
+
+### Cara Menjalankan Cluster (Docker)
+
+Kami telah menyediakan konfigurasi siap pakai di `docker-compose.cluster.yml`.
+
+1. **Build & Run Cluster**:
+
+   ```bash
+   docker-compose -f docker-compose.cluster.yml up --build
+   ```
+
+2. **Akses Aplikasi**:
+   Buka `http://localhost:8080`.
+   Nginx akan otomatis membagi request Anda ke `app-1` atau `app-2`.
+
+3. **Cek Status**:
+   ```bash
+   docker-compose -f docker-compose.cluster.yml ps
+   ```
+
+### Konfigurasi Rate Limiter Terdistribusi
+
+Middleware `src/middleware/rateLimit.ts` telah diupdate untuk menggunakan Redis Store.
+Ini artinya jika User A terkena limit di Server 1, dia juga akan terblokir di Server 2.
+
+```typescript
+// src/middleware/rateLimit.ts
+store: redis ? new RedisStore({ sendCommand: ... }) : undefined
+```
+
+---
+
+## 3. Tips Optimasi Lainnya
+
+- **Gunakan `.lean()` / Select**: Saat query database, selalu pilih field yang dibutuhkan saja.
+- **Compression**: Aktifkan gzip/brotli di Nginx (sudah ada di config default Nginx umumnya).
+- **Keep-Alive**: Gunakan koneksi database yang persistent (sudah dihandle oleh Prisma).