One of the questions that invariably pops up when discussing the Azuze Services Platform is: is it valuable for small organisations and how could they use it? This question is especially relevant in a country like Belgium, where even larger local businesses can be considered small by American standards.
For some reason, many people seem to equate Azure with traditional application service providers and/or hosters, along with the cost associated with such environments. Explain to them that they are wrong: Azure is especially relevant for small organisations, for several reasons.
Think about what it would take if you were a small organisation and wanted to set up a computing environment that would provide the following:
- Managed environment
- Always up-to-date platform
- Virtually infinite scalability with no added development cost
- On-demand scalability (think seasons…)
- Guaranteed SLA
- Higher than 4-nines availability
- Pay-per-use (although no pricing information has been made public by Microsoft, it would be fair to assume that cost will be based on a combination of use, up-time, and resources. If you were at the PDC, you will remember Ray Ozzie’s hat-tip to the Amazon team that pioneered such environments, and they offer a similar pricing model for their Elastic Compute Cloud)
- Higly secure with very minimal or no development effort
- Federated identity services
The price tag for even a small data center that would offer just a subset of these features is almost certainly way too high for any organisation below the multi-national level, to say nothing of the fact that some things – like on-demand scalability – are impossible to achieve without sufficient economies of scale. Only companies like Microsoft, Amazon, and Google are able to offer such scale.
So what would a (small) company use Azure for? My answer would be: any service that would require any combination of the above. It doesn’t really matter if you want to reuse that service for a single application or across several applications, or if you just want to use it for yourself or want to make it accessible to the outside world.
Think about the sort of things your software does, and how you could encapsulate (some of) that functionality into black-box-like services that can pretty much stand on their own: almost all of these would be ideal candidates to run on the Azure platform. Think about things like calculation engines, registration servcies, decision services, storage services, validation systems, profile servies, etc. Most of these are usually pretty well defined, well separated services that can be easily made into a standalone entity (and if you did the right thing when building them, they probably are already). Porting such building blocks to Azure would be a fairly simple effort.
Other good candidates are services that need temporary and/or high scalability. The more temporary and the higher the need fro scalability, the better. Anyone that’s ever tried to buy a ticket online whenever a popular act like U2, Bruce Springsteen, AC/DC (or Frans Bauer, if you’re so inclined…) announces a concert in Belgium knows what I’m talking about. Imagine having the capability to run a ticket reservation system on let’s say 2 servers for most of the time, then a few minutes before the U2 tickets go on sale scale that up to 200 servers, and 90 minutes later when all tickets have been sold out, go back to 2 servers.
100 times scalability up and down in a cycle that’s just a couple of hours long. Try and do that with you local datacenter…