Why ivi Switched from Sphinx to Elasticsearch
summary
The talk explains why the streaming service ivi migrated its search backend from Sphinx to Elasticsearch. It describes using the search engine as the core of the API and content-availability system, supporting per-region and per-platform indexes with different settings, content catalogs, rights-holder rules and advertising constraints.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 3:35Sphinx problems
- 9:58Why switch to Elasticsearch
- 13:30New system requirements
- 17:44Migration prep
- 19:30Early migration issues
- 26:16Fault tolerance testing
- 30:16Switching to Elasticsearch
- 35:54Results and outcomes
- 38:24Takeaways and advice
- 38:46Q&A
related talks
39mFlexible OpenSearch Data Management With Apache Iceberg: Data...
35mThings I Learned the Hard Way Building a Search Engine
42mGoing Elastic
39mCross Domain Enterprise Search - Content Diversity at Scale
01h 00mELK Stack - All You Need for Search In Your Applications
40mElasticSearch: Big Data, Search and Analytics
42mUsing Data Orchestration for speed, reliability and real-time content
38mKeynote: The Evolution of Data Infrastructure at Splunk