Here are some of the key core concepts you will come across when working with Weaviate, or vector databases in general.

Objects

An 'object' is an entry in a vector database.

A Weaviate object has three key components:

• ID: A unique identifier (in UUID format)
• Properties: Key/value pairs containing your actual data (like columns in a traditional database)
• Vector: A high-dimensional numerical representation (embedding) of the object's meaning

Like a 'row' in a relational database, each object represents a single "entry", or unit of information for storage and search.

note

In some cases, an object's properties and/or vector can be empty. However, the object must have an ID that is unique within its collection.

Collections

A 'collection' organizes objects into distinct sets of information, like a table in a relational database.

Each collection includes:

• Metadata (configuration): Defines the collection's structure and behavior, including AI model integrations and indexing strategies
• Indexes: Catalogs that speed up data retrieval and filtering
• Object store: Where your actual objects live

Collections let you organize different types of data separately. You might have one collection for "Movies," another for "Books," and a third for "User Reviews," each with its own objects, configuration and behavior.

What's next?

Objects and collections are the fundamental building blocks of Weaviate. Next, we'll explore how vectors, indexes, and the various APIs that make Weaviate's powerful search capabilities possible.