Reference
Dictionnary
11 fullstack terms, A to Z — what each one means, what it is for, and an example.
| Term | Category | Short definition | What it is for | Example |
|---|---|---|---|---|
| CI/CD | DevOps | Automated build, test and release on every push | Shipping small changes often without manual steps | push → build → deploy |
| CORS | Browser | Browser rules deciding who may call an API cross-origin | Opening your API to other domains without opening it to all | Access-Control-Allow-Origin |
| Endpoint | API | A single URL of an API that answers one operation | Naming and versioning each operation your service exposes | POST /api/words |
| Hydration | Rendering | Client JS attaching events and state to server-rendered HTML | Turning static markup into an interactive page after load | onclick fires after hydrate |
| JWT | Auth | A signed token that carries the session data itself | Validating a session without storing it on the server | Authorization: Bearer eyJ… |
| KV | Cloudflare | Key-value store optimised for very heavy read traffic | Configuration and data that is read far more often than written | word:kv → {...} |
| Middleware | Backend | Code that runs between the request and the final handler | Auth, logging and response rewriting in one shared place | hooks.server.ts → handle() |
| Migration | Database | A versioned script that applies one schema change | Reproducing the same schema across every environment | 0002_add_category.sql |
| ORM | Database | A layer that maps database tables to objects in your language | Querying and writing data without hand-written SQL | db.user.findMany() |
| REST API | API | An HTTP interface that exposes resources through URLs and verbs | Letting a frontend, a mobile app or a third party read and write your data | GET /api/words/jwt |
Page 1 of 2 · 11 terms