Loading video...

Video Failed to Load

Go Home

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 views • 1 year ago •via X (Twitter)

11 Comments

Santiago's profile picture
Santiago1 year ago

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.

Tembo - Multi-Workload Managed Postgres's profile picture
Tembo - Multi-Workload Managed Postgres2 years ago

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 :)

Gaius's profile picture
Gaius1 year ago

@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)

Santiago's profile picture
Santiago1 year ago

@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!

Tenkaizen's profile picture
Tenkaizen1 year ago

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

Alian's profile picture
Alian1 year ago

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

Jimi V. (Bitswired)'s profile picture
Jimi V. (Bitswired)1 year ago

@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.

Santiago's profile picture
Santiago1 year ago

@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.

Al Clark's profile picture
Al Clark1 year ago

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

Zachary Royals priv/acc's profile picture
Zachary Royals priv/acc1 year ago

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

Edrick🕗's profile picture
Edrick🕗1 year ago

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

Related 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 views • 4 months ago

New Course: ACP: Agent Communication Protocol Learn to build agents that communicate and collaborate across different frameworks using ACP in this short course built with IBM Research's BeeAI, and taught by Sandi Besen, AI Research Engineer & Ecosystem Lead at IBM, and Nicholas Renotte, Head of AI Developer Advocacy at IBM. Building a multi-agent system with agents built or used by different teams and organizations can become challenging. You may need to write custom integrations each time a team updates their agent design or changes their choice of agentic orchestration framework. The Agent Communication Protocol (ACP) is an open protocol that addresses this challenge by standardizing how agents communicate, using a unified RESTful interface that works across frameworks. In this protocol, you host an agent inside an ACP server, which handles requests from an ACP client and passes them to the appropriate agent. Using a standardized client-server interface allows multiple teams to reuse agents across projects. It also makes it easier to switch between frameworks, replace an agent with a new version, or update a multi-agent system without refactoring the entire system. In this course, you’ll learn to connect agents through ACP. You’ll understand the lifecycle of an ACP Agent and how it compares to other protocols, such as MCP (Model Context Protocol) and A2A (Agent-to-Agent). You’ll build ACP-compliant agents and implement both sequential and hierarchical workflows of multiple agents collaborating using ACP. Through hands-on exercises, you’ll build: - A RAG agent with CrewAI and wrap it inside an ACP server. - An ACP Client to make calls to the ACP server you created. - A sequential workflow that chains an ACP server, created with Smolagents, to the RAG agent. - A hierarchical workflow using a router agent that transforms user queries into tasks, delegated to agents available through ACP servers. - An agent that uses MCP to access tools and ACP to communicate with other agents. You’ll finish up by importing your ACP agents into the BeeAI platform, an open-source registry for discovering and sharing agents. ACP enables collaboration between agents across teams and organizations. By the end of this course, you’ll be able to build ACP agents and workflows that communicate and collaborate regardless of framework. Please sign up here:

Andrew Ng

105,343 views • 1 year ago

AG-UI makes building agentic applications dramatically easier. Here's how it works. This is a model for a simple chatbot: User → LLM → Response But interactive agents that render UI, pause for approvals, and ask users for input need a much more complex model. When building these agents, a response from the LLM will include a series of state changes as the agent runs: • Agent started a task • Agent called a tool • Agent updated its state • Agent streams these tokens • Agent is waiting on a human • Agent is resuming the task The Agent-User Interaction Protocol (AG-UI) treats the LLM response as a stream of events rather than a text endpoint. In practice, here is what you get as an agent runs: 1. Lifecycle events so your UI knows where the agent is. 2. Text messages that stream tokens. 3. Tool calls so your UI can prefill a form with any required arguments. 4. State updates that keep your UI in sync with the agent. 5. Special events for human approvals, rich media, and custom needs. All of these events travel over standard transports (SSE, WebSockets, or plain HTTP) as JSON. As a result, you can build a frontend that stays in sync with the agent's progress without having to invent a custom process to make this happen. For example, building a human-in-the-loop workflow becomes an off-the-shelf component you can integrate rather than build from scratch. CopilotKit🪁 is the creator of AG-UI, and you can use it when building frontend applications pretty much anywhere: • React • Angular • Vue • React Native • Slack • Teams • Discord • WhatsApp • Telegram Here is the link for you to check it out: Thanks to the CopilotKit team for partnering with me on this post.

Santiago

17,438 views • 14 days ago