Pick the items that are LLM application frameworks (not vector DBs, observability tools, or providers)

Multi-select·Easy·4.0 · 0·~1 min·Asked atAnthropic OpenAI Microsoft

Attempt it

The LLM stack has three distinct layers, and this question tests whether you can tell them apart. **Application frameworks** sit between your code and the provider's API. They give you composition primitives (chains, agents, retrievers, parsers), provider abstraction, observability hooks, and higher-order patterns like RAG. The four correct answers, LangChain, LlamaIndex, DSPy, and Mastra, are all frameworks. They wrap providers behind app-shaped primitives so you do not have to wire orchestration yourself. **Vector databases** store embeddings and do approximate nearest neighbour (ANN) search. Pinecone, Weaviate, Chroma, Qdrant, Milvus, pgvector. They handle storage and retrieval, not composition. A framework uses a vector DB; it is not one. **Observability platforms** capture traces from your LLM app and let you analyze them. Langfuse, LangSmith, Phoenix, Helicone, Weave. They sit alongside your app and watch what it does. They do not compose your chain. Each option in the question belongs to exactly one bucket. Pinecone is storage, Langfuse is observability, the other four are frameworks.

**Three layers of the LLM stack, one item per question.** - **LangChain**. Composition library (Runnables, LCEL pipe, agents, retrievers, parsers). Framework. - **LlamaIndex**. Data-centric framework (Documents, Nodes, Indexes, QueryEngines, ChatEngines). Framework. - **Pinecone**. Managed vector database (storage + ANN search). NOT a framework. - **DSPy**. Signatures + modules + optimizer compile loop; the 'compile your prompts, do not write them' framework. Framework. - **Langfuse**. Open-source observability platform (traces, evals, prompt management). NOT a framework. - **Mastra**. TypeScript-first agent + workflow framework with eval integration. Framework. **The discriminating question.** For each item: 'does this give me primitives that compose an LLM application, or does it sit alongside one'. LangChain composes via Runnables; LlamaIndex via data-centric indexes; DSPy via signatures and modules; Mastra via workflows and agents. Pinecone sits behind a framework, supplying retrieval. Langfuse sits alongside a framework, recording traces. Different roles. **Why the discrimination matters.** Stack architecture decisions hinge on getting these layers right. You pick a framework based on composition complexity, a vector DB based on scale and recall, an observability platform based on tracing surface and cost. Conflating them, 'we use Pinecone for our agents', signals a candidate has not touched the other layers.

Quick reference

TL;DR

Frameworks compose your app (LangChain, LlamaIndex, DSPy, Mastra). Vector DBs store embeddings (Pinecone). Observability tools watch traces (Langfuse). Different layers of the stack.

Memory aid

Easy to grasp

Picture building a house. The framework is the contractor who connects the rooms, wires the lights, and routes the plumbing. They put the pieces together. The vector DB is the warehouse next door that holds all your bricks and lumber. The contractor goes to the warehouse to fetch what they need, but the warehouse does not build the house. The observability tool is the security camera in the hallway, watching what happens inside the finished house. Useful, but it does not lay any bricks. App frameworks, storage, monitoring. Three different jobs, often confused.

Key concepts

LLM Frameworks RAG Vector Databases

Detailed answer & concept explanation

~5 min read

Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.

Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example.

Quick scan · 2–4 min

Everything important, quickly.

4 min: the three-layer model, why each correct option is a framework, why Pinecone and Langfuse are not, and how to pick within each layer.

Side-by-side

Layer	Role	Examples
App framework	Compose chains, agents, RAG; abstract providers	LangChain, LlamaIndex, DSPy, Mastra, Vercel AI SDK
Vector DB	Store embeddings; ANN search	Pinecone, Weaviate, Qdrant, Chroma, pgvector
Observability	Capture traces; evals; analytics	Langfuse, LangSmith, Phoenix, Helicone, Weave

Real-world examples

Real products, models, and research that use this idea.

Stripe and Notion engineering blog posts describe stacks with LangChain (or raw SDK) + Pinecone + Langfuse. Three distinct layers each picked separately.
Mastra's launch in 2025 filled the TypeScript framework gap that LangChain.js had not fully addressed; adoption tracks the agent + workflow + eval-first framing.
DSPy production deployments at Databricks and several research labs use it as the compile-time optimiser layered over a runtime that uses LangChain or raw SDK.
LangSmith vs Langfuse is the canonical 'pick your observability' decision; LangSmith is LangChain-native, Langfuse is OpenTelemetry-based.
Pinecone's serverless tier is a common 2026 default for vector storage in production RAG; the framework on top is decided separately.

Interviewer follow-ups

What an interviewer would ask next. Try answering before peeking at the approach.

QWhere do you put DSPy if your runtime is LangChain?

QWhen would you pick Vercel AI SDK over LangChain.js or Mastra?

QHow do you decide between Pinecone, Weaviate, and pgvector?

Don't say this

Red flags and common mistakes that signal junior thinking. Click to expand.

Most common mistake

Calling Pinecone or Langfuse a framework. That confuses storage and monitoring with composition, and signals only one slice of the stack has been built on.

60-second cheat sheet

The night-before-the-interview bullets. Scan these on the way to the call.

References

Primary sources. Skim if you want the original framing.