AI Weekly Malaysia

turbopuffer published the first post in a series on its upcoming v3 storage architecture, saying it is moving off a vector-primary design in which the ANN index is the primary index all other indexes and query plans revolve around, and making ANN 'just another' secondary index. The recap covers v1 (documents were only an ID and a vector, object storage as source of truth plus tiered NVMe SSD/memory caches, with Cursor and Notion named as early customers) and v2 (strong text and regex search, used by Linear for a syncing engine), and states the vector-primary layout has constrained query plans like GROUP BY and aggregations. No migration timeline, benchmarks, or pricing appear in this first update; the post is framed as setting the stage for following along.

Why: If you are choosing or already running a dedicated vector store, this is a concrete argument that a vector-first index can block SQL-style query plans (GROUP BY, aggregations) and hybrid text/regex work — so if your roadmap includes analytics or filtered aggregations over the same data as your embeddings, weigh that against a general query engine or Postgres+pgvector. Do not schedule anything from this post: it names no release date, no performance numbers, and no migration path, so the 'RIP, vector database' framing is positioning until v3 ships with measured results. Nothing in the text ties this to Malaysian or SEA infrastructure, pricing, or policy, so there is no local angle to act on yet.

A Reuters headline (dated 2026-09-28) says MongoDB's CEO is resigning to lead Meta's enterprise platform; the article body could not be read, so the successor, effective date, and terms are unconfirmed — the URL slug references "desai-steps-down-lead-metas-enterprise-platform". The Hacker News thread drew 262 points and 220 comments, so developer attention is real even though the excerpt contains no technical or product detail. Nothing in the available text states any change to MongoDB releases, Atlas pricing, licensing, or support commitments.

Why: There is no actionable detail here yet: no version, price, license, or roadmap change is stated, so a builder running MongoDB or Atlas should not change anything based on this item alone. The concrete decision is to wait for MongoDB's own confirmation of the new leadership and any stated direction before treating this as a signal about the database you depend on — the headline alone tells you a person is leaving, not that the product is changing.