Wrong confirmation ID

Loading…

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

CloudCoffee

by domgreen on May 09, 2010

#dddscot presentation on Windows Azure

#dddscot presentation on Windows Azure

http://domgreen.com	75
http://domgreen.posterous.com	4
http://www.slideshare.net	1
http://webcache.googleusercontent.com	1

Different types of storage - queue - blob - table
Azure Diagnostics logs locally firstIf you really want to use debugging in the cloud and have the money use the service bus
Cloud computing and the utility model leading to lower priceArchitects / devs now have to start considering the cost of azureJumping outside of the datacentre costs moneyOriginally designed to use the service bus – moved to interrole
Use the cloud as early into the development cycle as possiable - subtle differences in the way the dev fabric and the real cloud works - certifices are also a massive problem
Using memcached in azureVelocity will be in the future, hopefully will make cloud caching easy
Contain your cloudKeep from spreading around your applicationMuch like using a DALSingle point of contact for all your infrastructure needs
Multiple accounts on azure (can have dev test qa) - allows testing in the real environment no surprises here
Problem with testing out to large scaleDOS attacks assumed by cloudWill have to make the requests from within the cloud to get around thisNumber of tools currently being developed internally at MS
API is not testableNo interfaces (no mocking)Official line is that you should run in the fabric would add a lot of overhead to your build fileTime taken to spin this up added to running testsNeed to basically abstract all the api / libraryUnit testing in the cloud possibilities