LinkedIn Twitter Facebook
Lean, Kanban, Agile Pairing, TDD (sometimes test after) software architect and programmer. Worked with distributed (called cloud sometimes) computing services since 2007 using phat data (8 billion rows of data on an AVERAGE day, sometimes called big data) and everything from business intelligence to the nitty gritty of array structures inside file based data stores to create caching tiers for custom software needs. Currently pushing for distributed technologies & improving software architecture, better data centers, the best software development practices and keeping everything secure in the financial industry again. To see what I'm up to today, check out my blog at Composite Code.

3 responses to “Cloud Throw Down: Part 2 – Deployments and Instance Options”

  1. Andrew McGrath

    Adron,

    My understanding is that with AWS I can install msbuild.exe and run it whereas with Azure I can’t. This is important for us as we have built an APaaS (Application Platform as a Service) that uses msbuild.exe in the cloud to create and deploy the apps. Or maybe I am partly wrong in that I would have to have a “standalone server” with Amazon and then deploy via a fast gigabit+ connection into AWS.

    It’s all too new to me and we haven’t got as far as needing AWS or Azure just yet.

    Andrew

  2. Adrian Cockcroft

    You forgot the cluster compute and GPU options for EC2, also you should compare how easy and fast it is to automate deployment of 100 instances of a service (with Amazon we create an AMI and tell the autoscaler to make 100 of them using API calls).

  3. Cloud Throw Down: Part 3 – Relational Databases and Instance Prices

    […] Previous Throw Down… […]