Search Service of Twitter (2014)

This commit is contained in:
binhnguyennus 2018-01-28 12:20:09 +08:00
parent 536467233f
commit 8883dbb18d

View File

@ -112,7 +112,8 @@ A curated list of selected readings to illustrate Scalability, Availability, and
* [Search Architecture of eBay](http://www.cs.otago.ac.nz/homepages/andrew/papers/2017-8.pdf)
* [Nautilus: Travel Search Engine of Expedia](http://blog.expedia.com/expedias-nautilus-travel-search-engine-overview-and-applications/)
* [Galene: Search Architecture of LinkedIn](https://engineering.linkedin.com/search/did-you-mean-galene)
* [Search at Slack](https://slack.engineering/search-at-slack-431f8c80619e)
* [Search at Slack](https://slack.engineering/search-at-slack-431f8c80619e)
* [Search Service (Half a Trillion Documents and Query Average Latency < 100ms) at Twitter (2014)](https://blog.twitter.com/engineering/en_us/a/2014/building-a-complete-tweet-index.html)
* [Distributed Storage](http://highscalability.com/blog/2011/11/1/finding-the-right-data-solution-for-your-application-in-the.html)
* [In-memory Storage](https://medium.com/@denisanikin/what-an-in-memory-database-is-and-how-it-persists-data-efficiently-f43868cff4c1)
* [Optimizing Memcached Efficiency at Quora](https://engineering.quora.com/Optimizing-Memcached-Efficiency)