Top Stories cloudhacker
- When Azure Breaks: Lessons For Every Cloud Programmer
- Bees And Monkeys: 5 Cloud Lessons NAB Learned From AWS
- 'Don't Change Anything': A Problem With Cloud Computing
- How Will Privacy Law Changes Affect Cloud Computing?
- Why You Can't Just Switch To The Cloud Overnight
- Single-Purpose Clouds: The Next Step After Private, Public And Hybrid
Microsoft’s Azure cloud service aims for near-perfect uptime, but that doesn’t mean it is immune from major disasters. Here are some examples of the mistakes Microsoft has made that have caused Azure to temporarily break, and the lessons you can learn as a developer no matter what cloud platform you deploy.
The growth of cloud computing has revolutionised the way that information is produced, stored, processed and consumed, with privacy laws sometimes failing to keep up. From 12 March 2014, changes to Australia’s Privacy Act will impose new obligations on companies that collect and process personal information, including those that operate in the cloud.
One of the often-hyped advantages of the cloud is the speed with which you can deploy a new service. In theory, you can whack down your credit card details and instantly have something working. But in reality, any full-scale shift to the cloud is going to require a planning process that takes months, if not years.
We’ve become accustomed to the notion of public cloud services (freely available to everyone), private cloud services (maintained by a specific company, but charged and deployed on a usage/needs basis) and hybrid clouds (which blend the two). The next possible development on the cloud horizon? Single-purpose clouds, optimised for a particular kind of workload.
The most frequently-discussed elements of Amazon Web Services (AWS) are its EC2 virtual server options and S3 cloud storage. Yet some long-term AWS customers reserve their highest praise for a rather more obscure product: the Route 53 scalable DNS management service.
The government shutdown in the US means that many agencies are being forced to ‘bring down’ their web sites, even though actually leaving them in place would probably be cheaper. Those unusual circumstances deliver a lesson for everyone: using a demand-based cloud service can ensure you don’t end up stuck with excessive bills if you are forced to stop running sites or applications.