Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

I don't think specialized vector databases will survive for much longer. They were a big thing for a while, but now, you have pro-grade databases like MongoDB offering native support for vector search. If you don't understand how vector search is an absolutely bonkers, mind-blowing invention, watch the attached...

60,065 Aufrufe • vor 1 Jahr •via X (Twitter)

11 Kommentare

Profilbild von Santiago
Santiagovor 1 Jahr

The source code of every example is on this GitHub Repository: Every one of these AI examples uses MongoDB. You can run them all for free, change them, and start from there. Thanks to MongoDB for working with me on this post and sponsoring my work.

Profilbild von Tembo - Multi-Workload Managed Postgres
Tembo - Multi-Workload Managed Postgresvor 2 Jahren

It’d be cool if someone would make a specialized stack for each Postgres use case, with nice docs, perf comparisons, tutorials, etc - so you don’t have to leave Postgres :)

Profilbild von Gaius
Gaiusvor 1 Jahr

@MongoDB I have PTSD from using an early version of MongoDB on a project. Im a strong believer in using rock solid SQL databases, such as Postgres. And you can have vectors there too... (pgvector, etc)

Profilbild von Santiago
Santiagovor 1 Jahr

@MongoDB MongoDB is an acquired taste for those of us who came from a traditional RDBMS background. But it's pretty neat once you get the hang of it. And if MongoDB makes you uncomfortable, wait until I tell you about a one-table design using DynamoDB. Crazy stuff!

Profilbild von Tenkaizen
Tenkaizenvor 1 Jahr

@MongoDB Adapt or fade away, it's the law of the digital jungle

Profilbild von Alian
Alianvor 1 Jahr

@MongoDB Elasticsearch is also a great product, you can combine vector proximity, and bm25 with a lot of features and rerank off the shelf.

Profilbild von Jimi V. (Bitswired)
Jimi V. (Bitswired)vor 1 Jahr

@MongoDB that’s great, less moving parts. however I would definitely prefer having these features on a sql database. I know there are postgres and sqlite extensions but I lost track of their progress.

Profilbild von Santiago
Santiagovor 1 Jahr

@MongoDB Yes, Postgres support vectors as well through pgvector (extension). Not sure about MySQL, but I wouldn't be surprised if they have something like this as well.

Profilbild von Al Clark
Al Clarkvor 1 Jahr

@MongoDB yes, this a thousand times - there's just no need for it

Profilbild von Zachary Royals priv/acc
Zachary Royals priv/accvor 1 Jahr

@MongoDB Using PgVector, agreed vector databases are becoming less appropriate. A trad database with a vector extension seems to offer more flexibility and reliability.

Profilbild von Edrick🕗
Edrick🕗vor 1 Jahr

@MongoDB Mongodb is actually in a pretty good spot to offer this as a feature

Ähnliche Videos

Start building for an agent-first world. If you have a product, you need to start offering skills for Claude, Codex, Cursor, and any other agents. Your skills should specify: • How to navigate and use your product • Best practices the agent must follow • Detailed instructions on how to accomplish things • Anti-patterns to avoid Redis is one of the most popular in-memory data stores in the world, and they just released their agent skills. It takes one second to install, and it will turn your agent into a Senior Redis Engineer: $ npx skills add redis/agent-skills In the attached video, I show you how to install it as a plugin in Claude Code and some of its benefits. This is the easiest way to "teach" models what they don't know and keep their knowledge up to date. If you ask me, skills is literally one of the most brilliant ideas that Anthropic has put out there. If you use Redis, their skill is a must-have. If you don't, this skill will show you how to build and structure yours. Here is what their skill teaches your agent: 1. Current patterns for common use cases: caching, rate limiting, session management, vector search, semantic caching, pub/sub, streams. 2. Which data structure to use and when: hashes vs. JSON vs. sorted sets vs. vector sets. 3. Anti-patterns to avoid: no KEYS in loops, no unbounded key growth, no large values that amplify every operation. 4. Production-aware defaults: connection pooling, pipelining, cluster compatibility, error handling that doesn't silently swallow failures.

Santiago

37,546 Aufrufe • vor 5 Monaten