Hi everyone, thanks for coming. I know it's getting late in the day, and after all the hallway conversations and other talks you've been to, I start running out of steam. So I appreciate it. My name is Ryan Barrett, and I'm one of the co-founders of App Engine. I'm the lead on the datastore right now, and I'm here to talk about multihoming - running a service from multiple data centers. This kind of thing we do over the weekend when we get bored and have no parties to go to. So I figured we could tackle this last week and I'd give you a quick demo. So we're gonna be taking questions using a moderator. If you go to this URL code .com events i/o questions, go to the App Engine track and the transactions across data centers series, and feel free to type in questions, build on questions, all that good stuff. So let's get started. I'll start with a couple of quotes. One is from a guy named Eric Brewer, a computer science professor and former co-founder of Inktomi. He's well-known for his consistency, availability, partition tolerance theorem, which states that if you have a distributed storage system, this trade-off between consistency, availability, and partition tolerance is inherent and cannot be avoided. So it's something we need to pay attention to. The other quote is about making something scalable, which is just plain hard. There's no free lunch. You can use different technologies and techniques, which can take you a long way, but you can't ignore scalability altogether. Before I get started, I want to give you a presentation tip. Whenever I switch slides, people usually stop listening and start reading the slide. So what I want you all to do is turn away from me...
Award-winning PDF software
Video instructions and help with filling out and completing Which Form 8865 Transaction
