Pinecone is a fully managed, cloud-native vector database designed to store and query high-dimensional vector embeddings at production scale. It sits at the heart of modern AI pipelines β enabling semantic search, retrieval-augmented generation (RAG), recommendation engines, and anomaly detection β by finding the nearest neighbors of a query vector in milliseconds across billions of records. The critical mental model is that Pinecone is not a general-purpose database: you choose your distance metric and dimensionality at index-creation time and cannot change them, so aligning those choices with your embedding model upfront is the single most important architectural decision.
What This Cheat Sheet Covers
This topic spans 14 focused tables and 90 indexed concepts. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.
Table 1: Index Types β Serverless vs. Pod-Based
The choice of index type is the first and most consequential decision when working with Pinecone. Serverless is the default and recommended architecture for all new projects; pod-based indexes are legacy infrastructure no longer available to new customers as of August 2025.
| Type | Example | Description |
|---|---|---|
pc.create_index(name="my-index", dimension=1536, metric="cosine", spec=ServerlessSpec(cloud="aws", region="us-east-1")) | Separates compute from storage using immutable slab files on object storage; no pods, shards, or replicas to manage β scales automatically. | |
spec=ServerlessSpec(...),read_capacity={"nodes": 2, "type": "b1"} | Provisions exclusive memory + local SSD nodes on top of a serverless index for predictable low latency under sustained high QPS (thousands of queries/second). | |
spec=PodSpec(environment="us-east1-gcp", pod_type="p1.x1", pods=1) | Pre-provisioned infrastructure on dedicated pods; no longer available to new customers as of August 2025; existing users may keep using them. |