Skip to content

Topic

Vector Similarity Search

Approximate nearest-neighbour retrieval over embedding vectors, including HNSW indexing, distance metrics and recall/speed tuning.

Current stories

productOne report1 publisher

Agents are creating databases for a fixed number of administrators, pgEdge's CEO says

Stack Overflow's survey puts PostgreSQL first among developers' preferred databases for a fourth straight year. Databricks says agents spin up 80% of enterprise databases, so the planning number is databases per administrator.

Publishers:siliconangle.com

Reality

Evidence40
Adoption55
Hype gap+30
Incentives75
Confidence55
buildOne report1 publisher

Databricks isolates app and database limits in its Lakebase Search sizing test

Databricks tests Lakebase Search on 1M to 4M rows, using a 23,000-row internal app as its baseline. A search request touches two computes, the app's and the database's, and either one can set the limit.

Publishers:databricks.com

Reality

Evidence50
Adoption
Not scored
Hype gap+15
Incentives65
Confidence55
buildOne report1 publisher

S3 Vectors pre-filtering reaches existing indexes only after they move to ENHANCED mode

AWS says metadata pre-filtering in S3 Vectors returns up to 5x more matching vectors on highly selective filters, at no additional cost. Existing indexes keep CLASSIC search until updated, so multi-tenant RAG stores get the gain only after an index-mode switch.

Publishers:aws.amazon.com

Reality

Evidence45
Adoption
Not scored
Hype gap+25
Incentives70
Confidence55
buildOne report1 publisher

Plain-language questions push SEPA rulebook answers out of a top-5 vector search

One developer's test on 484 SEPA rulebook passages found that plain-English questions push several answers out of a top-5 vector search. Because the test measures each answer's rank directly, the failure shows up in retrieval, before the language model writes anything.

Publishers:dev.to

Reality

Evidence55
Adoption
Not scored
Hype gap0
Incentives
Not scored
Confidence45
buildOne report1 publisher

Full-precision embeddings push a 100-million-vector OpenSearch index to 1.3 TB of RAM

Amazon OpenSearch Service needs about 1.3 TB of resident RAM for 100 million 1,536-dimension FP32 vectors with one replica, a dev.to sizing post calculates. Raw vector values are about 98% of each entry, so the encoding picked before ingestion decides most of that memory and the node count behind it.

Publishers:dev.to

Reality

Evidence58
Adoption
Not scored
Hype gap+5
Incentives
Not scored
Confidence62
buildOne report1 publisher

Cloudflare AI Search goes GA with pixel-level image search and a November 1 billing start

Cloudflare made AI Search generally available with native image embeddings and PDF OCR, and will start billing for it on November 1, 2026. Which embedding model an instance runs now decides whether an image query searches pixels or a caption.

Reality

Evidence35
Adoption
Not scored
Hype gap+10
Incentives85
Confidence45
buildConfirmed2 publishers

Cohere says Embed 5 Fast keeps 98.4% of Pro's retrieval score when querying a Pro index

Cohere's Embed 5 lets teams index with Pro at $0.12 per million text tokens and query with Fast at $0.08 against the same vectors. The quality and throughput figures behind that split come from Cohere's own tests, run on datasets and parsing pipelines a buyer may not share.

Reality

Evidence45
Adoption
Not scored
Hype gap+20
Incentives75
Confidence55
buildOne report1 publisher

Throughline's recall receipts separate an empty archive from a search that never ran

Throughline's on-call agent returns a three-way coverage verdict with every memory recall, so a timed-out search cannot pass as "no prior incidents". Its author hit the same error-as-empty trap in CockroachDB's managed MCP server, where failures come back as HTTP 200.

Publishers:dev.to

Reality

Evidence35
Adoption
Not scored
Hype gap−10
Incentives30
Confidence40
buildOne report1 publisher

A substring-match scorer made a weekend RAG build look 13 points worse than it was

Exact-substring scoring put a developer's 700-line RAG tool at a 65% retrieval hit-rate at k=3, 13 points below what a token-overlap scorer found. The bug also made extra retrieved chunks look worthless, and a 20-question test set added 15 points of noise.

Publishers:dev.to

Reality

Evidence50
Adoption
Not scored
Hype gap+15
Incentives
Not scored
Confidence55
buildOne report1 publisher

Sentinel trains its fraud model on alerted-vs-cleared cases to stop double-counting the alert itself

Sentinel's builder trained its alert model on fraud versus cleared cases, reaching 0.9465 AUC after three passes that over-called fraud on every case. The finished agent lets an LLM write the explanation and leaves every action to fixed bank rules.

Publishers:dev.to

Reality

Evidence35
Adoption5
Hype gap+10
Incentives55
Confidence40
buildOne report1 publisher

Post-filtering a RAG query spends its LIMIT 10 on chunks the user cannot read

A dev.to walkthrough of a permission-aware Postgres project puts the ACL test in a CTE that the vector ranking reads from, so the nearest-neighbour search only ever orders rows the caller may see.

Publishers:dev.to

Reality

Evidence72
Adoption
Not scored
Hype gap+10
Incentives35
Confidence66
buildOne report1 publisher

Choosing the embedding model first locks the vec0 table to a fixed 768-dimension schema

A dev.to walkthrough replaces a managed vector store and a hosted embedding API with sqlite-vec and a local model on port 11434. Its schema declares float[768], so changing model dimension means re-embedding everything.

Publishers:dev.to

Reality

Evidence42
Adoption
Not scored
Hype gap+25
Incentives22
Confidence48
buildOne report1 publisher

Keying agent memory by session produced six copies of one test user's risk tolerance

A dev.to writeup by nasiko_labs describes a semantic memory tier whose first version inserted a row per session, so one agent could read "cautious" and "aggressive" at once. The rewrite keys each belief by fact type and archives the superseded version.

Publishers:dev.to

Reality

Evidence42
Adoption
Not scored
Hype gap+12
Incentives55
Confidence45
buildOne report1 publisher

Scoring 300 candidates in 35 milliseconds forces the LLM out of the request path

A dev.to post lays out a four-layer recommender and a 100 millisecond p99 budget with no slot for a generative call in the hot path. The figures are its author's own allocation, not a measurement from a running system.

Publishers:dev.to

Reality

Evidence38
Adoption
Not scored
Hype gap+15
Incentives
Not scored
Confidence45
buildOne report1 publisher

Three lines of trig let a DynamoDB vector index rank shops by great-circle distance

A dev.to test stores each shop's position as a unit-sphere triple and gets ordering that matches haversine to about half a metre across seven places, while the geohash index it was compared against missed the nearest shop.

Publishers:dev.to

Reality

Evidence62
Adoption
Not scored
Hype gap−10
Incentives45
Confidence55
buildOne report1 publisher

Grading a retriever starts with hand-labelling 500 queries against 100,000 chunks

Shrijith Venkatramana's embedding evaluation guide treats retrieval as a ranking problem scored with Recall@k, MRR and NDCG. Every figure in it is a worked example, and the labelling is the real bill.

Publishers:dev.to

Reality

Evidence58
Adoption
Not scored
Hype gap+8
Incentives50
Confidence52

Earlier coverage

  1. One error code explains why RAG pipelines keep a keyword index

    Build · September 18, 2026 · One report1 publisher

  2. Cosine similarity ranks the menu above the peanut allergy note

    Build · September 11, 2026 · One report1 publisher