← All speakers

Bio, Work & Ideas

Ben Flast

Conference affiliation: MongoDB · 2024

Ben Flast is a MongoDB director of product management focused on search, vector search, and AI integrations. He develops infrastructure that helps AI applications retrieve live operational data, preserve conversational context, and execute tasks without fragmenting information across separate systems.

In 2020, Flast worked on MongoDB’s data-lake products, including automated archiving and federated queries across Amazon S3. By 2023, he was product manager for Atlas Data Federation, helping developers address S3 partitioning and federated-query performance. His responsibilities subsequently expanded into search, vector retrieval, and tools for AI developers.

  • Keep retrieval close to operational data. Flast approaches retrieval-augmented generation through MongoDB’s document model: embeddings share records with customer information, application state, and conversation history, allowing semantic retrieval to incorporate live business context. His AI Engineer presentation details how MongoDB Atlas Vector Search combines HNSW indexes, metadata filters, similarity functions, and adjustable candidate counts.
  • Scale search independently while preserving shared context. Search Nodes separate vector-search infrastructure from transactional database resources, letting applications tune capacity without splitting their underlying data model.
  • Make application memory persistent and efficient. MongoDB-backed chat histories preserve continuity between conversations, while semantic caching can reuse answers to sufficiently similar requests and avoid additional model calls. Integrations with LangChain, LlamaIndex, Amazon Bedrock, Microsoft Semantic Kernel, and Haystack connect those capabilities to established development frameworks.
  • Give agents practical access to live systems. Flast contributes to MongoDB’s practical AI-agent curriculum, emphasizing database-backed tools, application records, and memory. He has also described the Model Context Protocol as a mechanism for connecting models with external databases, APIs, and services.

Read the topics behind these talks

1 conference talk

Key ideas

Scroll to read ↓

A useful AI application needs more than similar documents: MongoDB combines vector retrieval with the operational records, conversation history, and cache entries that supply application context.

  • Why an LLM cannot know your bank balance
    1:21 ↗
  • The standard RAG request path
    2:47 ↗
  • Documents hold richer application context
    3:26 ↗
  • Add embeddings to existing documents
    5:06 ↗
  • Query, tune, and filter retrieval
    6:18 ↗
  • Scale search separately from transactions
    7:10 ↗
  • Framework integrations beyond a vector store
    8:16 ↗
  • Reuse answers with a semantic cache
    9:11 ↗
  • Persist conversation history for continuity
    10:06 ↗
  • 4149 combines retrieval with operational memory
    10:46 ↗
  • Deploying the application on Atlas
    12:04 ↗

References