When I joined a startup already in progress as their first ops hire, I got a crash course in cloud operations. Running databases in EC2 without being on bare metal presents its own challenges; we also began using Hadoop and HBase on EMR, with tragicomic results. What monitoring existed was a twisty maze of half-measures, so improving our Mean Time To Lost Sleep required trying new tools and alerting strategies. And scaling performance meant relying on best practices and gut-feeling hunches.
This talk will have appeal for those curious about AWS, about using MapReduce in the cloud, and about whether MongoDB is really "web scale". (Spoiler alert: lolol.) Come for the EC2 trivia; stay for the table-flipping.
Notes and image credits: http://bridgetkromhout.com/speaking/2014/beyondthecode/notes/
3. We are the largest online video distributor of
international televised content streaming the
world's best movies, documentaries and TV
shows on demand with professional
subtitles.
@bridgetkromhout
4. Platform ops in public cloud?
Do you mean Platform
as a Service?
How is this different
from Infrastructure as a
Service?
@bridgetkromhout
12. Storage
No procurement delays!
All the IOPS!
No waiting!
Yes, cloud storage better
than the bad old days in
some ways, but with caveats.
@bridgetkromhout
13. Alphabet Soup: EBS, SSDs, pIOPS
Go with SSDs for your Elastic Block Store.
EBS-optimized instances = faster network
Provisioned IOPS: guaranteed, but prevent
bursting
@bridgetkromhout
14. Story Time!
Data stores and
sadness (as a service)
@bridgetkromhout
21. If it moves, we track it. Sometimes we’ll draw a graph
of something that isn’t moving yet, just in case it
decides to make a run for it. -- Ian Malpass, Etsy
@bridgetkromhout
measure all the things
22. So, back to this
platform stuff...
...how exactly do you
build and deploy it?
@bridgetkromhout
