Your SlideShare is downloading. ×
0
From "Overnight" to "Real-time": A Two-Year NoSQL Case Study
From "Overnight" to "Real-time": A Two-Year NoSQL Case Study
From "Overnight" to "Real-time": A Two-Year NoSQL Case Study
From "Overnight" to "Real-time": A Two-Year NoSQL Case Study
From "Overnight" to "Real-time": A Two-Year NoSQL Case Study
From "Overnight" to "Real-time": A Two-Year NoSQL Case Study
From "Overnight" to "Real-time": A Two-Year NoSQL Case Study
From "Overnight" to "Real-time": A Two-Year NoSQL Case Study
From "Overnight" to "Real-time": A Two-Year NoSQL Case Study
From "Overnight" to "Real-time": A Two-Year NoSQL Case Study
From "Overnight" to "Real-time": A Two-Year NoSQL Case Study
From "Overnight" to "Real-time": A Two-Year NoSQL Case Study
From "Overnight" to "Real-time": A Two-Year NoSQL Case Study
From "Overnight" to "Real-time": A Two-Year NoSQL Case Study
From "Overnight" to "Real-time": A Two-Year NoSQL Case Study
From "Overnight" to "Real-time": A Two-Year NoSQL Case Study
From "Overnight" to "Real-time": A Two-Year NoSQL Case Study
From "Overnight" to "Real-time": A Two-Year NoSQL Case Study
From "Overnight" to "Real-time": A Two-Year NoSQL Case Study
From "Overnight" to "Real-time": A Two-Year NoSQL Case Study
From "Overnight" to "Real-time": A Two-Year NoSQL Case Study
From "Overnight" to "Real-time": A Two-Year NoSQL Case Study
From "Overnight" to "Real-time": A Two-Year NoSQL Case Study
From "Overnight" to "Real-time": A Two-Year NoSQL Case Study
From "Overnight" to "Real-time": A Two-Year NoSQL Case Study
From "Overnight" to "Real-time": A Two-Year NoSQL Case Study
From "Overnight" to "Real-time": A Two-Year NoSQL Case Study
From "Overnight" to "Real-time": A Two-Year NoSQL Case Study
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

From "Overnight" to "Real-time": A Two-Year NoSQL Case Study

1,240

Published on

Meteor Solutions integrates site and advertising analytics to provide major publishers and advertisers the ability to identify and reach their influential visitors with advertising, exclusive content …

Meteor Solutions integrates site and advertising analytics to provide major publishers and advertisers the ability to identify and reach their influential visitors with advertising, exclusive content and rewards. Eighteen months ago, Meteor was backed by a relational DB and struggling to keep up with volumes in a batch processing environment that was ill-suited to our graph oriented data model. Today, the service is backed by Cloudant, a distributed document store based on CouchDB, and provides deeper analytics in real-time. This transition enabled 10x growth and allowed us to open our technology to a much broader range of applications -- though not without some bumps along the way. This talk will cover:

Overview of our services and specific technical challenges
Overview of Cloudant/CouchDB, how we leverage it, and its relation to other SQL, NoSQL, and web technologies in our stack
Benefits we've seen and tradeoffs we have had to make
Operational lessons learned
Future plans: how NoSQL's possibilities and limitations influence business, product and operational decisions

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,240
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. 2 years of nosql benjamin anderson @banjiewen meteor solutions, inc.
  • 2. about meteor
  • 3. our data
  • 4. 2009pretty simple
  • 5. why this was bad
  • 6. enter couchdb/cloudant (and some redis)
  • 7. nosql in production
  • 8. what we’ve learned
  • 9. solved initial problems
  • 10. introduced new ones
  • 11. problemsno documentation
  • 12. problemsno documentation
  • 13. problemsyou probably don’t need data model flexibility
  • 14. problemsad-hoc data analysis is challenging
  • 15. problems predictability
  • 16. problems library support
  • 17. problems not unsolvable!
  • 18. overall, good stuff
  • 19. good stuff rapid iteration
  • 20. good stufffanatical customer support
  • 21. good stuffgood people want to work on it
  • 22. good stuffhorizontal scalability is no joke
  • 23. good stuffsolves real problems
  • 24. we’ve learned a lot
  • 25. what we’ve learned pay for the support
  • 26. what we’ve learned expect tradeoffs
  • 27. what we’ve learned you probably don’t need it
  • 28. thanks benjamin anderson @banjiewenmeteor solutions, inc.

×