Your SlideShare is downloading. ×
Nosqlpresentation
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Nosqlpresentation

105
views

Published on

Published in: Business, Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
105
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
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
  • Speed
  • Not really, depends on how you use it.
  • Not really, depends on how you use it.
  • Not really, depends on how you use it.
  • Can add new fields without database schema migration. Zero downtime. The catch is, if your document layout changes, you HAVE to migrate.
  • Can add new fields without database schema migration. Zero downtime. The catch is, if your document layout changes, you HAVE to migrate.
  • Online media is a 24/7 operation.
  • Queues – stats, logs, user actions NoSQL is not the only way, RDBMS can still be used for mission-critical data
  • Transcript

    • 1. Data in the Newsroom: Architectural Decisions. Recap.
    • 2. Agenda
      • Reasons
      • Goals
      • Approaches
      • Redis
    • 3. Why?
    • 4. WHY?!
    • 5.  
    • 6. Speed
      • Not really
    • 7. Speed
      • Not really
      • No more join pain
    • 8. Speed
      • Not really
      • No more join pain
      • Faster document delivery
    • 9.  
    • 10. Flexibility
      • Add new fields at will
    • 11. Flexibility
      • Add new fields at will
      • No joins means easy horizontal scaling – just add more metal
    • 12. Goals
      • Availability for users
      • Availability for producers
      • Developer quality of life
    • 13.  
    • 14. Approach
      • Queuing
      • Caching
      • Separate read/write instances
      • Don’t sweat non-vital data loss
      • NoSQL, NoReligion
    • 15.  
    • 16. Redis is Lush
      • Close-to-the-metal, hardcore, no holds barred, shredding-fast key-value store
      • IT ACTUALLY HAS TRANSACTIONS. TRUE STORY!
      • As cache
      • Storing user data
      • Gets an “up” vote for collecting voting data
      • Replication from the future
    • 17. Redis More FTW
      • Messaging – PUB/SUB
      • Native INCR operator
      • Native scheduling
      • TRANSACTIONS
    • 18.  
    • 19.