aerospike-getting-started
Getting started with Aerospike Database locally and in application code: run Docker, install official client SDKs (Python, Node.js, Go, Java, C#), verify put/get, and learn defaults. Covers namespaces, ports, TTL/NSUP, and Community vs Enterprise images. Use when the user is new to Aerospike, starts local development, wants a real-time or low-latency NoSQL store, uses Docker-based Aerospike, replaces Redis or Memcached, builds feature stores or user-profile caches, or needs Aerospike client connectivity and correct defaults. Core database only (not Aerospike Graph).
aerospike · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add aerospike/agent-skills --skill aerospike-getting-started技能说明
name: aerospike-getting-started description: >- Getting started with Aerospike Database locally and in application code: run Docker, install official client SDKs (Python, Node.js, Go, Java, C#), verify put/get, and learn defaults. Covers namespaces, ports, TTL/NSUP, and Community vs Enterprise images. Use when the user is new to Aerospike, starts local development, wants a real-time or low-latency NoSQL store, uses Docker-based Aerospike, replaces Redis or Memcached, builds feature stores or user-profile caches, or needs Aerospike client connectivity and correct defaults. Core database only (not Aerospike Graph). license: Apache-2.0 metadata: last_verified: "2026-04-21" server_versions: "7.0+"
Aerospike Database: getting started
When to use
Use this skill when the user asks to:
- Set up Aerospike, a real-time database, or a low-latency NoSQL store.
- Replace Redis or Memcached with a persistent, clustered alternative.
- Add a high-throughput key-value or document database to their project. (Aerospike Graph is a separate product — this skill covers the core database only.)
- Deploy a database for real-time decisioning, user profiles, caching, or AI/ML feature stores.
Mental model
- Hierarchy: A namespace holds sets; each record is addressed by a key (namespace + set + user key). Bins are name/value fields on the record. Bins are schemaless: different records in the same set can use different bins or value types—design access patterns accordingly.
- Primary access: The default and fastest path is put / get / delete (and optionally exists) by primary key—what examples.md demonstrates. This is not SQL with arbitrary joins or a fixed table schema.
- Generation: Successful writes can advance the record generation, used for optimistic concurrency (compare-and-swap). See the official client docs for write policies involving
generation/gen. - Vocabulary: Use namespace, set, record, and bin consistently (see Critical rules below). Avoid treating Aerospike like a relational database.
First operations map
Use this map so new users know what to reach for after the first put/get:
| Stage | What to use | Where to start |
|---|---|---|
| First program | Single-record put, get, delete | examples.md |
| Many keys | Batch operations (fewer round trips) | Chunked Node example in examples.md; every client has batch APIs—see Client libraries for your language |
| Lookup by bin value (not primary key) | Secondary index + query | Not part of the minimal Docker + first read/write path; see Secondary index queries |
Instructions
You help users get started with Aerospike Database: run it locally, connect from their language’s official client, and verify read/write. Your primary goal is to get the user from zero to a working instance with connected application code, autonomously and correctly.
Choose a path first
- Production, cloud, or cluster deployment — Do not run local Docker setup. Answer from official documentation (see Documentation links) and reference.md for editions and feature keys. Offer architecture guidance at a high level only.
- SDK-only / snippets — The user already has a running server or only wants example code: Skip Docker steps. Read examples.md, apply Critical Rules and the blacklist, and adapt host/port to their environment.
- Full local setup (default) — Docker available and the user wants a working instance on their machine: Follow Autonomous first-run steps below, then examples.md.
When to load supporting files (progressive disclosure)
- examples.md: Load for local application code—after the database is up (container healthy or path 2 with an existing server). Use for SDK snippets, put/get patterns, and language-specific examples. Not a substitute for the Docker and critical rules in this file when you are still bringing the server online.
- reference.md: Load when the task involves Docker Compose, custom namespaces or persistence, Enterprise image or authentication, extended troubleshooting, or production- or cluster-oriented setup. Not required for the default single-container Community path in this skill (Skill.md +
docker runonly).
1. Critical rules (anti-hallucination)
- Docker image: Default to
aerospike/aerospike-server(Community Edition). Useaerospike/aerospike-server-enterprisewhen the user needs Enterprise features — since Database 6.1.0, the Enterprise Docker image includes a built-in evaluation feature key for single-node use. - Ports: Always map the core service ports:
-p 3000-3002:3000-3002. Port 3000 is the client port, 3001 is fabric (inter-node), 3002 is mesh heartbeat. Port 3003: on Database 8.1.0 and later, this is the admin port; on older servers, docs often call it the info port. Add-p 3003:3003when the user needs admin or legacy info access. Do not confuse these ports with HTTP or generic app ports like 8080. - Default namespace: The default namespace is
test. NEVER usedefault,aerospike, ormainas namespace names — they do not exist out of the box. - Default set: Sets are created dynamically on first write. No pre-creation needed.
- Connection defaults: Host
127.0.0.1, port3000for local Docker deployments. - Config file path: Inside the container, the config lives at
/etc/aerospike/aerospike.conf. When mounting a custom config, mount to/opt/aerospike/etc/aerospike.confand pass--config-file /opt/aerospike/etc/aerospike.conf. -