Database / Weaviate Vector database Interview questions
What is the difference between bringing your own vectors and using a vectorizer module?
Using a vectorizer module means Weaviate calls out to a configured embedding provider automatically, both when objects are inserted and when a text-based query (like near_text) is issued, so the application only ever deals with raw text or other source data, never raw vector arrays directly.
| Vectorizer module | Bring your own vectors |
| Weaviate calls an embedding provider automatically. | Application computes and supplies vectors itself. |
| Simpler application code; works directly with text. | More control over exactly which embedding model and version is used. |
| Depends on network access to the configured embedding provider. | No dependency on Weaviate having access to any external embedding service. |
Bringing your own vectors (configuring vectorizer: none) is the right choice when an application already has an embedding pipeline elsewhere (perhaps using a custom fine-tuned model, or a provider without a built-in Weaviate module), or when strict control over exactly which model version produced every vector matters more than the convenience of automatic embedding generation.
Using a vectorizer module means the application:
Bringing your own vectors is the right choice when:
More Related questions...
