Atlas - owl vs deer

Talk given by MetaBroadcast's Engineer Fred van den Driessche. Jun 19th, 2013.

Transcript

1. Atlas 4.0 owl vs deer Fred van den Driessche Engineer @fredvdd
2. What is Atlas? “the global video and audio index”
3. What is Atlas? • aggregates metadata from multiple sources • stores in a uniform model • APIs + feeds provide consolidated data
4. What is Atlas? ATLAS DB BBC PA C4 etc... /content /schedules /topics sitemaps radioplayer interlinking
5. Atlas Data Model brand item series version broadcast location
6. History •2008: 0.5 • MySQL • URIs • RDF • POST to Update • /content
7. History •2009: 1.0 • Adapters • POST to Update
8. History •2010: 2.0 “otter” • MongoDB • denormalization • /discover • /schedules • uploading
9. History •2011: 3.0 “owl” • MongoDB :-( • less denormalization • /discover • annotations
10. DEMO
11. Objectives for 4.0 “deer” Easy scaling • Discovery • Faster updates • More consistent, rational API • extensive use of HTTP
12. External Changes - quite small • IDs not URIs • URL structures: /content/<id> not /content?uri=<uri> • More flexible filtering • Better annotations • Richer output • Better error handling • Consistently fast
13. Internal Changes - almost everything • New Technologies • New Persistence Layer • Flexible Denormalisation • Bootstrapping • Queue
14. DEMO
15. Optional Extras • improvements to storage and indexing • monitor all the things • small core • decentralization • queue-triggered processing • all data submitted via POST? • generalization of feed output • new equivalence algorithm?
16. Questions? more at http://atlas.metabroadcast.com follow @mb_atlas