- Who we are and what we do
- Our blogs
- What's azure
- Slide showing all of azure and all the crazy services
- Highlight the bits of the diagram we're going to use
- Diagram of the application
- Discuss the various different parts and how each one of them scales under load
- how does DNS work?
- TTL? Time to lunch?
- what are our other DNS options?
- DNS almost finishes up all the services needed to do everything within azure (SSL and domain registration)
- still lots of need for batch processing (month end processing, file processing)
- how does this differ from other compute services/when to use batch over web jobs
- what batch is built on top of
- what is table storage (column store)
- how does this differ from relational databases?
- how can we fit this information into an application?
- super super cheap
- elastic search vs azure search
- how we're going to use this
- the usefulness of centralized logging
- logstash, kibana, logship
- docker
- how to integrate with azure services
- how autoscale works
- what limits to set
- demo of autoscale try to force a scaling event
- how to use metrics other than what azure offers (monitor and then use the api)
- stop asking me so many questions, I'm tired and want supper