Notion's Vector Search Is Excellent. Their Next Problem Is Harder.
Blog post from Zilliz
Notion's engineering journey over the past two years has showcased significant advancements in vector search infrastructure, highlighting their successful transition from pod clusters to a serverless model and further to a turbopuffer system, resulting in a 90% reduction in costs. Despite these achievements, the company faces future challenges in enhancing their AI capabilities, particularly concerning serverless limitations, the real-time and offline data processing dichotomy, and offline context engineering. The architectural shifts, such as storage-compute separation and the adoption of a Lambda architecture, have optimized current operations but also revealed potential bottlenecks in performance and system integration. The forthcoming challenges will involve addressing the complexities of maintaining user memory, precomputing knowledge graphs, and processing data signals efficiently to improve AI retrieval and context enrichment, which remain critical for scaling AI applications beyond the existing infrastructure.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| Vector Search | 20 | 1,977 | 499 | 171 | -39% |
| Real-time | 11 | 7,450 | 1,704 | 292 | -47% |
| Serverless | 11 | 798 | 252 | 108 | -40% |
| LLM | 1 | 6,889 | 1,263 | 265 | -9% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.