# Core concepts

The application concepts behind records, transactions, memory, coordination and Particles.

Source: https://particledb.ai/getting-started/concepts/

## Records and schemas

Tables store typed records. Schemas group tables within a database. Choose stable primary keys and types that match how the application uses each value. [Tables and schemas](/getting-started/databases-and-schemas/).

## Transactions

A transaction groups database changes that must succeed or fail together. Keep transactions short. Retry the whole transaction after a retryable conflict; do not retry an external action blindly. [Transactions](/sql/transactions/).

## Search and memory

An embedding describes a record in vector form. A vector query finds nearby embeddings; relational filters narrow the candidate records. Generate embeddings consistently and use the same dimensions for stored vectors and queries. [Search and memory](/guides/search-and-memory/).

## Key-value

Keys are useful for short identifiers, counters and expiring data. Key-value access is a separate interface from ordinary table queries; check supported commands and atomicity boundaries before building coordination on it. [Key-value](/guides/key-value/).

## Particles

A Particle is custom code callable from SQL. Its inputs, outputs, privileges and execution limits form part of your application's database contract. [Particles](/particles/overview/).

## Analytics

Aggregations answer questions about operational records without requiring an export to a separate system. Indexes, data size and query shape still affect response time. [Analytics](/guides/analytics/).

## Interfaces and guarantees

One server offers several interfaces: SQL clients, the HTTP API, Redis-compatible clients and the native SDKs. Do not assume that transactions, authentication or values are interchangeable across separate connections; consult [connection addresses](/installation/ports/) and the reference for your client. [Transactions](/sql/transactions/), [durability](/operations/durability/) and [limits](/reference/limits/) describe the observable application contract rather than storage internals.

## Related

[Documentation home](/docs/) · [Troubleshooting](/guides/troubleshooting/)
