Are you running a database in the cloud? Worried that you're doing it wrong?
Engine Yard supports a broad set of databases with flexibility for customers to modify and configure. However, freedom to adapt and extend standard functionality comes with unexpected negative consequences: modifications can seriously affect durability and performance. I've observed common problems, patterns and best practices with big (and not so big) data. I'll highlight the most common pitfalls and discuss how to avoid them.
Video for this talk is available here: http://vimeo.com/83755776
20. Anti-Pattern #5
Often means at least
one write per request
Tables have a
tendency to bloat
RDBMS for
Any DB issue/task may
Session
cause app to hang
Data
25. We have a cloud deployment!
Happy team on shipping day, lmfao if you don’t celebrate like this
26. Obvious statement #2
Databases can live in
the cloud quite well
Many IaaS, PaaS,
DBaaS options
Cloud-based
databases,
they are real
Easy to get started
may be economical
30. Anti-Pattern #10
Instance storage is
not persisted (use
EBS)
Data locality matters
Storage is
the same
Don’t run your cloud
DBs too hot!
31. Doing cloud right
Know your
cloud
deployments
Replication in the
cloud is a must-have
Put DB master
replicas in different
AZs
32. Doing cloud right
Learn high
availability
disaster
recovery
Get good at replica
promotions (some
work involved)
Understand and
invest in DR/HA.
Know your options
33. Doing cloud right
Invest in monitoring
Know baseline
behavior
Know your
system
Know your data
distribution
querying patterns