Building a full-text search engine in 150 lines of Python code - blog / HN

see also

• Books about full text search?
  • Relevant Search
• Inverted index is a database index storing a mapping from content, such as words or numbers, to its locations in a table, or in a document.
• relevant search
  • How Google Code Search Worked - Regular Expression Matching with a Trigram Index
• SQLite FTS

The Boyer-Moore Fast String Searching Algorithm / HN

ElasticSearch / lucene index

• Stack Overflow: The Architecture - 2016 Edition - The main reason we’re on Elasticsearch instead of something like SQL full-text search is scalability and better allocation of money.
  • A new search engine for Stack Exchange - After the performance problems we have run into with Lucene.NET we’ve decided to make a change, we’re moving the network on to elasticsearch. - Stack Overflow Migrate Architecture from .NET Framework to .NET Core - Stack Overflow Architecture

SQL CPUs are comparatively very expensive, Elastic is cheap and has far more features these days. Why not Solr? We want to search across the entire network (many indexes at once), and this wasn’t supported at decision time. The reason we’re not on 2.x yet is a major change to “types” means we need to reindex everything to upgrade. I just don’t have enough time to make the needed changes and migration plan yet.

What is Apache SolrCloud?

• Apache Solr vs Elasticsearch

Lucene

• Text search with Lucene / 2
• What is in a Lucene index? (Adrien Grand)

How does Google search engine work?

• The Anatomy of a Large-Scale Hypertextual Web Search Engine
• Google Architecture