Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
new proposal Amsterdam by Martin Englund
- Loading branch information
drozer
committed
Apr 4, 2013
1 parent
c838bec
commit 50f2bce
Showing
1 changed file
with
23 additions
and
0 deletions.
There are no files selected for viewing
23 changes: 23 additions & 0 deletions
23
...ls/MartinEnglund_AmazontimetravelorhowtolivewithAWSeventualconsistencytimewarps/index.txt
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
--- | ||
extension: html | ||
filter: | ||
- erb | ||
- markdown | ||
dirty: true | ||
proposal: true | ||
talk: true | ||
selected: false | ||
layout: event | ||
author: Martin Englund | ||
title: "Amazon time travel, or how to live with AWS eventual consistency time warps" | ||
--- | ||
|
||
**Abstract:** | ||
During the development of the BOSH AWS cloud provider interface[1] we have been exposed to the ugly side of the AWS eventual consistency - which also got me into a headed argument with the Clouderati about (bad) API design. This presentation will show you the pitfalls of heavy use of AWS, why the current AWS eventual consistency model is flawed, how to work around it, and how BOSH now can scale out a deployment on AWS from 0 to 400 VMs in 10 minutes. | ||
|
||
[1] <https://github.com/cloudfoundry/bosh> | ||
|
||
**Speaker:** | ||
|
||
Contact: Martin Englund | ||
http://blog.codenursery.com/ |