March 2015 | 13 hours 40 minutes | AAC 48KHz, mono, s16, 127 kb/s | AVC1, 1920x1080, 1921 kb/s, 16000.00 fps | 18.9 GB
Helping architects map what they know already into public cloud platforms like AWS and Azure. A lot of what they know translates well, but there are some easy mistakes to make because there are some surprising differences in architecting for the cloud. This talk will introduce some of the most important differences, introduced first as mistakes (anti-patterns), then how to do it right.
This workshop is a high level workshop covering the philosophies behind re-architecting systems on the fly and v2 syndrome. We'll focus on a couple of case studies regarding re-architecture, and strategies to make it successful. We expect people to leave this workshop with a framework and some background by which to approach legacy systems, and how to improve, evolve, or change them out.
In some organizations, architects are dismissed as people that draw box and arrow diagrams - the dreaded whiteboard architect. While we don't want to foster that stereotype, it is important for an architect to be able to construct basic architectural diagrams. An architect must also be able to separate the wheat from the chaff eliminating those models that don't help tell the story.