Disrupting Full Text Search Industry With JavaScript
summary
A JavaScript full‑text engine called Orama implements Patricia trees, pluggable data‑structures and insertion/search hooks, runs in browser, Node and Deno with no dependencies, and serves isomorphic apps. Benchmarks show indexing 20k products and remote queries in ~38 ms, local queries down to ~1 ms and individual lookups around 200 μs. A single PR that changes array‑intersection logic delivers a 50% performance gain, proving JS micro‑optimizations and runtime‑aware patterns matter.
AI-written summary · about
chapters (16)
- 0:00Introduction to talk
- 0:42Love for Elasticsearch
- 2:05Pain points with Elasticsearch
- 3:33Goals for new search engine
- 4:14Learning full text search theory
- 5:17Choosing JavaScript over other languages
- 6:45JavaScript performance insights
- 8:30Array intersection optimization
- 9:11JavaScript runtime optimizations
- 10:53Fast properties in JavaScript
- 11:56Creating Orama search engine
- 13:17Orama features overview
- 14:41Extensible architecture of Orama
- 15:46Live demo of Orama
- 17:11Why Orama competes with giants
- 18:15Call to action and Q&A
related talks
23mThe Faster, The Cheaper
27mLyra: Disrupting full-text search industry with JavaScript
28mLyra: Disrupting the full-text search industry with JS
41mAn introduction to search-index.js
41mScaling Search and Powering Vector-Based Retrieval With OpenSea...
57mOptimizing Frontend Performance of a High-Load Search
26mImmutability, interactivity & JavaScript
35mNoSQL, No Server, No problem: Using ORM's in Javascript Applications