aerospike
- 6 skills
- 0 followers
- 14 hours ago last updated
- ▌ Port To Jdk8 · aerospikePort changes from a stage-based branch to a stage-jdk8-based branch, adapting Java 21 code to Java 8 compatibility
- ▌ Port To Jdk21 · aerospikePort changes from a stage-jdk8-based branch to a stage-based branch, upgrading Java 8 code to Java 21
- ▌ Aerospike · aerospikeWork with the Aerospike core database end to end — run a local instance with Docker and verify a first write and read, build or review client code with the official SDKs (Python, Node.js, Go, Java, C#), and design or review a data model, whether from requirements or against a schema that already exists. Covers namespaces, sets, bins, primary key design, TTL and NSUP, collection data types, expressions, secondary indexes, batch and scan workflows, client policies, connection pooling, record sizing, and schema deliverables. Use when the user sets up Aerospike, writes or debugs Aerospike client code, chooses keys or models data for it, reviews an Aerospike schema before building, or evaluates it as a persistent replacement for Redis or Memcached in real-time, low-latency, feature-store, or user-profile workloads. Core database only — not Aerospike Graph, and not cluster operations, sizing, XDR, or backup and restore, which belong to Aerospike Operations documentation.
- ▌ Aerospike Development · aerospike bundleGuides Aerospike application development with official clients for Java/Go/Python/C#/Node.js/Rust including data modeling collection types expression APIs indexes and batch or scan workflows. Use when users build or review client code or tune data access against a model that already exists. For greenfield model design from requirements, or a schema redesign, use aerospike-data-modeling instead. Redirect cluster deployment sizing XDR and backup questions to Aerospike Operations documentation. Core database only; not Aerospike Graph.
- ▌ Aerospike Data Modeling · aerospike bundleDesigns a new Aerospike data model from requirements, producing a schema guide and schema summary: record granularity, key design, bin structure, relationship and consolidation decisions, and index strategy. Use when no schema exists yet, when redesigning an existing model, or when reviewing a proposed schema for structural defects. This is design-time work that precedes code. For writing or reviewing client code against a model that already exists, or for client APIs, policies, CDT operations, and expression usage, use aerospike-development instead. Core database only; not Aerospike Graph.
- ▌ Aerospike Getting Started · aerospike bundleGetting 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).