Tag: Cloud Computing

  • Cloud Common Sense

    Common sense is needed in, or outside of, the cloud.

    The byline for this piece about cloud computingis great. It a sarcastic comment about problems in the cloud, and if you read it, then maybe you won’t think every problem in the cloud is cause for the complete abandonment of cloud computing as a tool in your technology toolbelt. As cloud vendors grow, they often standardize and build more homogenous infrastructures that could have cascading failures. We’ve seen this in the past with hosting companies that provided data center services, and we’ve seen it in large companies that centralize and standardize their systems.

    When I started my career, I saw in in mainframe computing as well. That was more amusing as we would all stand up in our cubes, and if you saw a significant number of others standing up, you knew the entire mainframe was down. These days I think Twitter lets us know as quick as any monitoring software when there’s a large outage. That’s assuming Twitter isn’t down.

    Whether you move to the cloud, outsource any services to another company, or even host your physical servers in someone’s data center, you need to use common sense for your architecture, security, and monitoring. If you don’t control the physical hardware, you must be more diligent about security. If you move data around, be aware of security controls and implement tunnels or strong encryption. Above all, make sure you have good backups at your location, and away from the cloud provider. If the worst case scenario happens, you should still have your data.

    The cloud isn’t for every situation, just like outsourced data centers or IT services aren’t for every company. However there are a lot of advantages to moving to a cloud environment, and it may reduce costs. That last item might be enough for your company to force moves to the cloud, despite objections from sysadmins and DBAs. Learning more about cloud computing and services like SQL Azure is a skill that DBAs ought to consider. Even if cloud computing isn’t likely in your industry, you might find yourself in a different industry next year.

    Steve Jones


    The Voice of the DBA Podcasts

  • The Special Cloud

    A new Amazon cloud for the US government

    It’s not a short yellow bus special cloud, at least I hope not. Amazon is introducing a cloud for the US government, designed to meet their regulatory and compliance requirements. The idea here is that there are different needs for some sensitive information that the US government deals with, or at least some departments. I think most of us recognize this might be the case, and the same cloud infrastructure that some company like SQLServerCentral needs wouldn’t be appropriate for OSHA or some other department.

    Amazon introduced this US only cloud that is physically and logically accessible in the US only and adheres to some alphabet soup of regulatory requirements. It should allow more government organizations to store or process data in a cloud environment. I think this is a good move on Amazon’s part, and a potential benefit for some US agencies that might process lots of data at times, but not want the overhead of a large IT infrastructure to maintain permanently.

    This is a good step in the evolution of cloud computing, and I hope that Microsoft and other vendors start to develop specialized clouds as well. There are PCI compliant hosting services, but I can imagine that there might be semi-private clouds for medical, research, or other specialized data sets, which conform to the specific security and regulatory need of that industry. At some point I can imagine that Amazon or Microsoft might have parts of their data centers partitioned into different industry verticals that provide services according to different criteria.

    The cloud can provide a great place for periodic and bursty workloads for many applications and companies, but there are definitely security concerns that need to be addressed. The development of specific clouds for specialized needs seems to be a positive step in allowing more companies to take advantage of cloud computing in the future.

    Steve Jones


    The Voice of the DBA Podcasts

  • The Woes of Cloud Computing

    Cloud computing: sunshine or rain?

    Many people have been skeptical about the move to cloud computing, especially in the database world. There are valid reasons to worry about security, legal issues, and more. I certainly think that using cloud services requires some planning and careful examination of the impact to your environment, but I also think that many companies will want to make the move, so it pays to learn more about cloud computing and be prepared with realistic, rational concerns from the database perspective.

    Anthony Skipper of ServiceMesh gave a presentation on some of the problems and lessons learned from moving to cloud computing. It was picked up in an Information Week piece that summarizes some of the areas that can cause problems for your company. The list of issues is a good one, and worth reading through.

    There are a couple of items in the list that I thought were very interesting for data professionals. The first was the fact that companies need to ensure that they implement policy from the beginning for how cloud services will be used. I think this will always be a point of contention between IT and the clients, and this isn’t an excuse to lock down clients or limit their options. Instead it ought to be a place where IT looks to be informed, help with guidance, and respond more quickly to client requests. IT cannot be the stumbling block in the cloud, or it will get left behind.

    The other thing? This quote: Have the ability to bring things back internally or to another provider at any point. That’s a great point. The cloud isn’t the ultimate answer, and you ought to have a backup plan, which should include the ability to move your services back to your own data center.

    Steve Jones


    The Voice of the DBA Podcasts

  • Cost of the Cloud

    Will we get real time costing of our cloud computing?

    One of the benefits of moving to a cloud infrastructure for IT services should be a reduced cost. The economies of scale for having specialized staff, licensing, etc. are more evident when you have more of everything. The larger you are, the more efficient you ought to be. For some companies, this can be achieved internally because they have such a large number of computers, but for many companies, I think they seriously struggle with the cost of staff and infrastructure for technology.

    A company that looks to build a technology infrastructure has to make an investment and across a short period of time, they are locked into the hardware that has been purchased. Often we find individual departments are unsure they are receiving a fair share of the IT services, which has resulted in large chargeback systems being implemented that usually have a lot of overhead.

    Microsoft appears to be trying to deal with this in an interesting way. It has collected, and published, very detailed data on how the services in its data centers are being used. These are essentially a private cloud for many business units at Microsoft, and the ability to see how costs are being spent in applications, services, even help desk tickets, which can drive behavior.

    Developers now have an incentive to build better applications, since the cost of a poorly performing application is more easily determined. I would even assume that accounting for metrics in development environments should help people test different solutions, and perhaps even start to determine when one should spend more time optimizing code and when someone should allocate more hardware.

    I don’t know if other cloud computing vendors will start to offer detailed use analysis and charges for the use of their services, but I expect that if they did, it would be something that many CFOs, and CTOs might want to see in analyzing the value they get from their public, or private cloud infrastructures. I know that I’ve found value in all the detailed metrics that we get in costing SQL Server queries through DMVs, wait states, and other metrics, which can certainly help one write code much more efficiently.

    Steve Jones


    The Voice of the DBA Podcasts