What is/isn’t this talk about? > Not an introduction to Polyglot Persistence > More about how and why with practical examples > Looking at it more in terms of developer point of view
Advantages > Tapping into the strengths of each data storage technology > One of the key drivers towards componentization component based architecture > Sometimes, it’s the only way
Living Examples: Foursquare > Mainly on MongoDB, Elasticsearch and Hadoop > Search, recommendation, social graph, listing, ratings and reviews, venue detail > More on engineering.foursquare.com
Living Examples: Zleek > MongoDB as the primary source of truth > Elasticsearch for answering search questions and log data > Neo4j for recommendation and answering interesting questions > Future: Redis for caching
Living Examples: Zleek - Neo4j > Syncing the data from MongoDB > Questions to answer: • Which grocery store has the ingredients for a recipe? • Which recipes can be made with the items in a store? • How my friends interacted with this recipe?
One last thing... “Well-tune the requirements, consider the trade offs and come up with a solid, functional plan to serve your data instead of blindly getting them out through the same door.
Here is more information > Polyglot Persistence from Martin Fowler http://martinfowler.com/bliki/PolyglotPersistence.html > An evolving example: https://github.com/tugberkugurlu/ModernShopping