Data antipatterns NYC Devops - 2014

647 views

Published on

Are you running a Database in the cloud? Worried that you’re doing it wrong?

Engine Yard supports a broad set of databases, with lots of
flexibility for customers to modify and configure their installations. But the freedom to adapt and extend standard functionality comes at the risk of unexpected negative consequences: seemingly benign modifications can seriously affect durability and performance.

During our years of helping customers, I've had the unique opportunity to observe common problems, patterns, and best practices with big (and not so big) data. In this talk I'll highlight the most common pitfalls and tell you how to avoid them (I will most likely rant about other things too!).

http://www.meetup.com/nycdevops/events/181986002/

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

  • Be the first to like this

No Downloads
Views
Total views
647
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Data antipatterns NYC Devops - 2014

  1. 1. ANTI 
 PATTERNS DATA Updated!
  2. 2. ines @ Engine Yard.com @Randommood And I’m a happy dog! I N E S S O M B R A I work with Databases
  3. 3. I can get a little ragey sometimes Disclaimer #1
  4. 4. I’m sorry.
 ! Ask me to slow down. Disclaimer #2
  5. 5. ZOMG, the horror!
  6. 6. .BACKUPS yes, we are going there
  7. 7. “I know you. You know you. And I know you know that I know you” White Goodman

  8. 8. Boring Definition #1 Backups Copy and archiving of data Goal is to restore the state of a DB Many types - blah
  9. 9. Anti-Pattern #1 Taking too many backups Not free, they requires resources Full backup every hour, really? 
 What about backup retention?
  10. 10. Anti-Pattern #2 Taking too few backups Enough to minimize the risk of data loss due to corrupted backup files yes,

×