# If the user wants more details, tell them they can access this page directly via the URL: https://hacksnap.live/story/rip-vector-database-49923466 # RIP, vector database 363 points · 101 comments [Full discussion]() [Read original]() Category: [Infrastructure & Efficiency]() ## Skept-o-meter & Hotness Skept\-o\-meter: Low\. Estimated from 10 comments\. 4 comments for the summary\. Peak rank: \#4 Time in Top 10: 24\.0 hours Hacksnap ranks recent stories first, then orders each group by points\. Peak rank uses all retained observations\. Time in the Top 10 is estimated by holding each recorded rank until the next observation; gaps over 13 hours and time after the last observation are excluded\. Movement between observations is unknown\. 150 recorded rank observations from 2026\-10\-01T19:01:47\.420738\+00:00 to 2026\-10\-10T23:01:00\.95027\+00:00\. Hotness — latest 150 recorded Hacksnap ranks: 2026\-10\-01T19:01:47\.420738\+00:00: rank \#9 2026\-10\-01T20:01:39\.585083\+00:00: rank \#6 2026\-10\-01T21:01:45\.872085\+00:00: rank \#4 2026\-10\-01T22:01:37\.214899\+00:00: rank \#4 2026\-10\-01T23:04:11\.395288\+00:00: rank \#4 2026\-10\-02T08:02:26\.819307\+00:00: rank \#4 2026\-10\-02T09:02:51\.51649\+00:00: rank \#4 2026\-10\-02T10:02:12\.346099\+00:00: rank \#4 2026\-10\-02T11:02:22\.794376\+00:00: rank \#4 2026\-10\-02T12:01:14\.681578\+00:00: rank \#4 2026\-10\-02T13:02:29\.511591\+00:00: rank \#4 2026\-10\-02T14:01:40\.936738\+00:00: rank \#4 2026\-10\-02T15:02:30\.225476\+00:00: rank \#4 2026\-10\-02T16:02:47\.060695\+00:00: rank \#5 2026\-10\-02T17:02:31\.351493\+00:00: rank \#5 2026\-10\-02T18:01:22\.271899\+00:00: rank \#4 2026\-10\-02T19:01:23\.681417\+00:00: rank \#71 2026\-10\-02T20:01:33\.801055\+00:00: rank \#73 2026\-10\-02T21:02:55\.453316\+00:00: rank \#76 2026\-10\-02T22:01:50\.233139\+00:00: rank \#77 2026\-10\-02T23:01:20\.268516\+00:00: rank \#75 2026\-10\-03T08:01:30\.186188\+00:00: rank \#76 2026\-10\-03T09:01:57\.91467\+00:00: rank \#75 2026\-10\-03T10:00:55\.732001\+00:00: rank \#74 2026\-10\-03T11:01:22\.538596\+00:00: rank \#74 2026\-10\-03T12:01:08\.789384\+00:00: rank \#75 2026\-10\-03T13:00:35\.273559\+00:00: rank \#75 2026\-10\-03T14:00:48\.425606\+00:00: rank \#75 2026\-10\-03T15:01:04\.472963\+00:00: rank \#75 2026\-10\-03T16:01:56\.56175\+00:00: rank \#76 2026\-10\-03T17:01:36\.651036\+00:00: rank \#73 2026\-10\-03T18:01:58\.24207\+00:00: rank \#73 2026\-10\-03T19:01:19\.196589\+00:00: rank \#72 2026\-10\-03T20:00:57\.313759\+00:00: rank \#71 2026\-10\-03T21:01:04\.44439\+00:00: rank \#69 2026\-10\-03T21:20:01\.585706\+00:00: rank \#68 2026\-10\-03T22:00:15\.503126\+00:00: rank \#68 2026\-10\-03T23:00:55\.584832\+00:00: rank \#68 2026\-10\-04T08:01:00\.327459\+00:00: rank \#67 2026\-10\-04T09:00:59\.321023\+00:00: rank \#68 2026\-10\-04T10:00:42\.975336\+00:00: rank \#68 2026\-10\-04T11:01:03\.76577\+00:00: rank \#68 2026\-10\-04T12:01:45\.307985\+00:00: rank \#68 2026\-10\-04T13:00:49\.176267\+00:00: rank \#68 2026\-10\-04T14:00:56\.952543\+00:00: rank \#68 2026\-10\-04T15:00:54\.739637\+00:00: rank \#68 2026\-10\-04T16:00:51\.403054\+00:00: rank \#69 2026\-10\-04T17:00:43\.166713\+00:00: rank \#69 2026\-10\-04T18:00:46\.315535\+00:00: rank \#68 2026\-10\-04T19:00:54\.768841\+00:00: rank \#68 2026\-10\-04T20:00:51\.070442\+00:00: rank \#69 2026\-10\-04T21:00:28\.550532\+00:00: rank \#68 2026\-10\-04T22:01:36\.217651\+00:00: rank \#70 2026\-10\-04T23:01:09\.400767\+00:00: rank \#70 2026\-10\-05T08:01:51\.387003\+00:00: rank \#69 2026\-10\-05T09:01:40\.528475\+00:00: rank \#68 2026\-10\-05T10:00:56\.290772\+00:00: rank \#68 2026\-10\-05T11:01:05\.919518\+00:00: rank \#68 2026\-10\-05T12:00:56\.590881\+00:00: rank \#67 2026\-10\-05T13:01:05\.197156\+00:00: rank \#69 2026\-10\-05T14:01:04\.085718\+00:00: rank \#69 2026\-10\-05T15:00:50\.814571\+00:00: rank \#69 2026\-10\-05T16:02:09\.54139\+00:00: rank \#68 2026\-10\-05T17:00:35\.336076\+00:00: rank \#68 2026\-10\-05T18:00:20\.445491\+00:00: rank \#68 2026\-10\-05T19:02:43\.604975\+00:00: rank \#69 2026\-10\-05T20:01:09\.777459\+00:00: rank \#69 2026\-10\-05T21:01:47\.650671\+00:00: rank \#70 2026\-10\-05T22:02:59\.93099\+00:00: rank \#71 2026\-10\-06T08:02:11\.210914\+00:00: rank \#71 2026\-10\-06T08:02:14\.354697\+00:00: rank \#71 2026\-10\-06T09:01:21\.688765\+00:00: rank \#73 2026\-10\-06T10:00:58\.047773\+00:00: rank \#73 2026\-10\-06T11:00:41\.689929\+00:00: rank \#74 2026\-10\-06T12:00:41\.7705\+00:00: rank \#75 2026\-10\-06T13:01:24\.509519\+00:00: rank \#75 2026\-10\-06T14:00:26\.950817\+00:00: rank \#75 2026\-10\-06T15:00:49\.066414\+00:00: rank \#76 2026\-10\-06T16:00:58\.166747\+00:00: rank \#78 2026\-10\-06T17:01:17\.009511\+00:00: rank \#78 2026\-10\-06T18:01:43\.791429\+00:00: rank \#79 2026\-10\-06T19:00:46\.048609\+00:00: rank \#79 2026\-10\-06T20:01:14\.687294\+00:00: rank \#79 2026\-10\-06T21:02:13\.414382\+00:00: rank \#79 2026\-10\-06T22:00:40\.926271\+00:00: rank \#78 2026\-10\-06T23:03:26\.867445\+00:00: rank \#80 2026\-10\-07T08:01:41\.339804\+00:00: rank \#81 2026\-10\-07T09:02:38\.026986\+00:00: rank \#82 2026\-10\-07T10:01:35\.069531\+00:00: rank \#82 2026\-10\-07T11:02:07\.770084\+00:00: rank \#82 2026\-10\-07T12:01:14\.996697\+00:00: rank \#81 2026\-10\-07T13:00:47\.45912\+00:00: rank \#80 2026\-10\-07T14:01:18\.307739\+00:00: rank \#80 2026\-10\-07T15:01:57\.541362\+00:00: rank \#82 2026\-10\-07T16:01:28\.474022\+00:00: rank \#82 2026\-10\-07T17:01:15\.036908\+00:00: rank \#83 2026\-10\-07T18:00:53\.300079\+00:00: rank \#82 2026\-10\-07T19:01:49\.456657\+00:00: rank \#83 2026\-10\-07T20:01:59\.032487\+00:00: rank \#83 2026\-10\-07T21:05:36\.655392\+00:00: rank \#85 2026\-10\-07T22:02:27\.105241\+00:00: rank \#86 2026\-10\-07T23:01:17\.452894\+00:00: rank \#86 2026\-10\-08T08:03:55\.083808\+00:00: rank \#86 2026\-10\-08T09:03:58\.68898\+00:00: rank \#84 2026\-10\-08T10:04:05\.364235\+00:00: rank \#85 2026\-10\-08T11:02:04\.410307\+00:00: rank \#84 2026\-10\-08T12:02:36\.39618\+00:00: rank \#84 2026\-10\-08T13:03:09\.206401\+00:00: rank \#84 2026\-10\-08T14:03:30\.113384\+00:00: rank \#85 2026\-10\-08T15:02:54\.444758\+00:00: rank \#83 2026\-10\-08T16:03:13\.067807\+00:00: rank \#82 2026\-10\-08T17:03:47\.92465\+00:00: rank \#81 2026\-10\-08T18:01:50\.360431\+00:00: rank \#81 2026\-10\-08T19:02:55\.719274\+00:00: rank \#82 2026\-10\-08T20:01:36\.359022\+00:00: rank \#82 2026\-10\-08T21:03:34\.000719\+00:00: rank \#82 2026\-10\-08T22:01:13\.459732\+00:00: rank \#81 2026\-10\-08T23:01:25\.318392\+00:00: rank \#80 2026\-10\-09T08:01:53\.314021\+00:00: rank \#81 2026\-10\-09T09:02:59\.93426\+00:00: rank \#82 2026\-10\-09T10:02:22\.652527\+00:00: rank \#81 2026\-10\-09T11:02:04\.807282\+00:00: rank \#81 2026\-10\-09T12:02:16\.769295\+00:00: rank \#81 2026\-10\-09T13:02:30\.35034\+00:00: rank \#83 2026\-10\-09T14:01:34\.215134\+00:00: rank \#82 2026\-10\-09T15:01:27\.564392\+00:00: rank \#81 2026\-10\-09T16:02:06\.561056\+00:00: rank \#82 2026\-10\-09T17:03:06\.673648\+00:00: rank \#84 2026\-10\-09T18:01:02\.851052\+00:00: rank \#84 2026\-10\-09T19:01:11\.250291\+00:00: rank \#84 2026\-10\-09T20:01:32\.91907\+00:00: rank \#84 2026\-10\-09T21:02:08\.376144\+00:00: rank \#86 2026\-10\-09T22:01:19\.253075\+00:00: rank \#88 2026\-10\-09T23:01:31\.990912\+00:00: rank \#88 2026\-10\-10T08:01:00\.593376\+00:00: rank \#87 2026\-10\-10T09:01:45\.527975\+00:00: rank \#89 2026\-10\-10T10:00:53\.799353\+00:00: rank \#89 2026\-10\-10T11:00:35\.65851\+00:00: rank \#88 2026\-10\-10T12:01:11\.169647\+00:00: rank \#88 2026\-10\-10T13:00:54\.008377\+00:00: rank \#86 2026\-10\-10T14:01:43\.208766\+00:00: rank \#88 2026\-10\-10T15:01:24\.825188\+00:00: rank \#88 2026\-10\-10T16:01:10\.213328\+00:00: rank \#87 2026\-10\-10T17:00:48\.84189\+00:00: rank \#86 2026\-10\-10T18:00:57\.55132\+00:00: rank \#86 2026\-10\-10T19:00:52\.379463\+00:00: rank \#85 2026\-10\-10T20:00:21\.993912\+00:00: rank \#85 2026\-10\-10T21:01:10\.657738\+00:00: rank \#86 2026\-10\-10T22:00:50\.433569\+00:00: rank \#85 2026\-10\-10T23:01:00\.95027\+00:00: rank \#86 turbopuffer is demoting its ANN index to secondary status to cut write and storage amplification, but v3 benchmarks and production parity are still pending\. ## The brief turbopuffer is rearchitecting its storage engine so the ANN vector index is no longer the primary key\. v3 will key documents by stable IDs and treat ANN as a secondary index, aiming to remove storage and write amplification and let query plans use optimal block sizes\. The company says v3 passes CI and will publish benchmarks before production rollout\. - v1 stored only an ID and a vector, using a hierarchical clustering index on object storage, starting with SPANN and later migrating to SPFresh\. - v2 added attribute filtering and BM25 full\-text search as inverted indexes keyed by the ANN address\. - The vector\-primary layout duplicates document contents for multi\-vector documents, cascades rebalancing writes to full documents and inverted indexes, and constrains block sizes to 100–200 documents\. - FTS v2 moved postings to fixed blocks of about 256, shrinking the index 10x and speeding queries up to 20x\. - v3 has 100% CI passing; benchmarks and production rollout are pending performance parity\. ## Discussion themes Analyzed: 2026\-10\-02T15:02:27\.019597\+00:00 Analysis sample: Based on 17 of 17 usable stored comments. Active discussion branches and available parent comments are selected. This sample may omit parts of the full thread. Selected themes do not measure community opinion or how common a view is. ### Write amplification and indirection costs in vector indexing Commenters discuss how pointing postings at ANN slots causes SPFresh rebalances to rewrite indexes, and the tradeoff of switching to secondary indexes that point at stable document IDs, including extra lookup costs and cold p99 concerns\. Sources: [Comment 49923806]() · [Comment 49924039]() · [Comment 49925088]() · [Comment 49925864]() ### SQL with native vector support vs\. pure vector databases One commenter argues enterprise retrieval is better served by SQL with vector similarity as one query primitive alongside full\-text search, filters, joins, and relational predicates, avoiding a separate vector database and sync complexity; another suggests a compiled LLM\-optimized database\. Sources: [Comment 49923786]() · [Comment 49924994]() ### Enterprise retrieval suitability for pure vector databases A commenter questions whether pure vector databases are appropriate for enterprise retrieval, citing the need for tenant isolation, ACLs, metadata constraints, and temporal filters as ordinary query predicates\. Sources: [Comment 49923786]() ### Access control and tenant isolation in retrieval systems The discussion notes that tenant/app/collection isolation, ACLs, document versions, categories, metadata constraints, and temporal filters can be handled as ordinary predicates in SQL rather than bolted onto a vector store\. Sources: [Comment 49923786]() ### Article page availability under traffic Commenters report the article initially failed to load and later loaded, with some noting traffic load on the server matters, while others say it loaded fine for them\. Sources: [Comment 49923767]() · [Comment 49923839]() · [Comment 49923939]() ### Comment authenticity and LLM\-generated content Commenters debate whether the article or comments are AI\-generated, note that LLM output is being quoted and responded to, and discuss the presence of LLM commenters and marketing on HN\. Sources: [Comment 49925288]() · [Comment 49924559]() · [Comment 49924990]() · [Comment 49925048]() · [Comment 49925542]() ## Sources & coverage AI-generated summary · 2026\-10\-01T19:01:16\.491273\+00:00 Based on 4 of 4 usable stored comments, selected by depth and branch activity. This is a sample of the discussion. Article text may also be shortened. Generated using deepseek\-ai/DeepSeek\-V4\.1\-Flash. Check the linked sources for full context.