1. Architectural lessons learned from refactoring a
Solr based API application.
Torsten Bøgh Köster (Shopping24) Apache Lucene Eurocon, 19.10.2011
2. Contents
Shopping24 and it‘s API
Technical scaling solutions
Sharding
Caching
Solr Cores
„Elastic“ infrastructure
business requirements as key
factor
3. @tboeghk
Software- and systems- architect
2 years experience with Solr
3 years experience with Lucene
Team of 7 Java developers currently at Shopping24
8. index fact time
•16 Gig Data
•Single-Core-Layout
•Up to 17s response time
•Machine size limited
•Stalled at solr version 1.4
•API designed for small
tools
10. ask the nerds
„Shard!“
That‘ll be fun!
„Use spare compute cores at Amazon?“
breathe load into the cloud
„Reduce that index size“
„Get rid of those long running queries!“