Showing posts with label Cloud computing. Show all posts

Azure forming a cloud: Ask Why, What, Where, When, and How

Join me at the kick-off lunch event of the Azure in the Cloud user group on Thursday, March 3rd at Microsoft in Irving. Register at http://azureinthecloud.blogspot.com/ or  https://www.clicktoattend.com/invitation.aspx?code=153957

It will be a great introduction to Azure; and even if you are quite experienced, my hope is that you will find it interesting and inspiring.


.
Join us for our
Kick-off Lunch Event


Date:
Time:

Location:
Thursday, March 3, 2011
11:30am – 1:30pm
Lunch will be provided
Microsoft Office, Irving - Visual Basic 4060 Conf. Room

 

Register Today! Click Here





Azure Forming a Cloud: Ask Why, What, Where, When, and How
   By Greg Cowin


Be a part of the premier User Group featuring Windows Azure.

Come for lunch and meet with others as we seek to:
+ Understand Windows Azure as it evolves
+ Share techniques, patterns, trends, and practices
+ Connect with people that have a cloud strategy






What is the federal government's new policy on cloud computing?

The new policy is "cloud first." Recently, the White House announced plans for a "cloud first" policy with the goal of eliminating at least 800 of the government's 2,100 data centers by 2015.

The federal plan was released by federal CIO Vivek Jundra. This plan involves shifting some work to commercial, private and government-run cloud computing systems.

The plan: 25 Point Implementation Plan To Reform Federal IT



Two ideas to help your company move to the cloud


Here are a two ideas to help your company move to the cloud. While these ideas are more specific to migrating to Windows Azure, you can adopt the approach for any offering:

1. Portfolio Assessment
2. Application Assessment and TOC Analysis



Portfolio Assessment
The idea: classify your portfolio of applications into three categories based on migration effort.

Category 1: Small Effort
It mostly just requires re-packaging for Azure—a fairly straight forward migration.
Examples: ASP.NET Apps, WCF Services, Web Services, Simple SQL Server deployments, etc.

Category 2: Medium Effort
Fairly easy but requires some to moderate code changes.
Examples: moderate use of file system, dependency on SQL features such as SSIS, SSRS, etc.

Category 3: Large Effort
Probably would require a re-write anyway. Installed as Administrator, uses unmanaged code; extensive use of registry, etc.
Examples: Legacy ASP, C++ app, extensive use of file system and registry.

Once the applications are classified, then applications from category 1 and 2 can be further analyzed and eventually migrated. The cost of moving a category 1 application will usually fall within a small range of effort. Category 2 apps will need to be estimated on a case-by-case basis.

To analyze a portfolio of applications, you need a simple set of assessment questions to handle the higher volume.

Application (or System) Assessment
The idea: use a much deeper set of questions and total cost of ownership analysis. It will help you understand the effort involved in the migration. A TOC analysis can help you understand the amount of money that you will save for a particular application—usually over a 3-5 year period. It can be significant. It is difficult to compete with the economies of scale that cloud providers such as Microsoft can provider, because Microsoft is buying 1 out of 4 servers in the US and 1 out of 3 in the world.

Closing
Best of luck azure getting into the cloud and let me know if I can help make recommendation.

Ultimately, you will need to get your feet wet by doing an application assessment and migration.


The cloud is great design and unstoppable. Even though it is unstoppable, it will take time.

Top 3 reasons why cloud computing is unstoppable

In my view, here are the top 3 reasons why cloud computing is unstoppable:

1. Business Continuity
2. Operational Agility
3. Cost


Business Continuity
Business continuity is about ensuring that critical business functions can continue smoothly not only in the event of disaster, but other events such as acquisitions, moves, bankruptcies, getting a large customer, loss of key personnel, loss of a large customer, etc. All can cause havoc on business continuity. These events are critically important to business stakeholders—the people ultimately in charge of how IT money is spent.

Today, the pace of business change is significant: new product offerings, uptakes, downturns, acquisitions, geographic expansion, moves, exponential growth, spikes, campaigns, etc.

Imagine a scenario: you acquire a company with a mess of servers, network, cabling, and software installs. It takes time to move these systems and components into a parent company—many times failing completely. The desire of the parent company is to incorporate the acquisitions and hit the gas pedal, but it is often slow and affects business continuity.

Some companies are financed in hopes of being acquired as an exit strategy, but the back end simply is not structured for it. You could be a lot more desirable to be acquired if you have standard deployments in the cloud.

Imagine that you are a small to medium-sized business and your biggest customer, a Fortune 50 company, wants to use your solution for their entire company. In this kind of deal, a software escrow agreement will not be enough; they will want your solution to be in the cloud. So that in the event that your company goes under, they can just take ownership. They acquire this virtual property as opposed to trying to figure out a mess of software and hardware that is hard-coded to a particular location with odd configuration and deployment.

The cloud, particularly Platform as a Service (PaaS), provides key mechanisms to help with business continuity: elasticity, redundancy, standard deployments, etc. You are protected against disaster, able to scale up or down within minutes, not weeks, months, or years. The standardized deployments are easily understood and can be smoothly transitioned to a new team—not a mess of custom scripts, installs, and manual error-prone magic.

For example, Windows Azure provides triple redundancy of the Azure Storage and SQL Azure. It keeps three synchronized copies. This is often never done even for critical systems because of the complexity and expense of having redundant data centers. Azure maintains three copies of your data and can failover to another geographic location. It is built into their Cloud OS—really the fabric of the cloud.

In my view, the killer benefit of cloud computing is business continuity.

Operational Agility
Especially with Platform as a Service (PaaS) such as with Microsoft Azure, operation agility is achieved by providing an architecture that can easily scale horizontally. You can dynamically allocate these containers of services up or down. You can be much more efficient with just the capacity that you need with a pay-for-use model.

If you are deploying on virtual machines or physical machines, you must plan for peak capacity. Planning for peak capacity can be manageable if your load is consistent, but is usually a challenge. Ideally, you plan for an efficient amount of over capacity. This can be very difficult—impossible to estimate. Often times driven by fear, systems are dramatically over deployed—not efficiently over deployed.

This kind of operational agility will change business models. My understanding is that Pixar has recently deployed RenderMan into the cloud and is able to burst it when needed to make a movie and make it available as a service to smaller studios.

The ability to burst out to 1000's of computing containers then back to zero will create new business opportunities—even for the little guys.

Cost
It is easy to spend 1/2 million bucks on a few servers, SANs, load balancers, network equipment, racks. Make it redundant and then double that along with your provider rates. It is a big capital expenditure and it will still have to wait weeks until it is ready to be used and much longer for complex issues to be resolved.

With the cloud, it is a pay-for-use model without the huge upfront capital expenditures. You can leverage economies of scale and best practices. Microsoft has invested 8 billion in their cloud initiative. Based on a platform briefing that I attended at Microsoft, they are buying 1 out of 4 servers in the US and 1 out of 3 servers world-wide. How can you compete with this economy of scale.

The starting retail price for Windows Azure currently costs 5 cents per computing hour. Everyone that I have dealt with has a 70%+ savings in total cost of ownership. It is significant.

Closing
Manufacturing companies used to maintain their own power plants in the early days of the industrial revolution, now, everyone uses and trusts power as a utility. In my view, Windows Azure is far closer to utility computing than any other cloud provider. You do not have to maintain the stack. It provides elasticity of demand. You have a utility of computing and storage containers.

The same will be true for industrial computing, it will take a while, but it will happen. Don't wait too long, because someday you might have a 30% cut in your IT budget and it will hurt because you will be upside down.

I have been working with Microsoft Azure. Microsoft Azure has all three. In my view, Microsoft is the clear leader in cloud computing or more broadly, IT as a Service that includes SaaS (Software as a Service), PaaS (Platform as a Service), and IaaS (Infrastructure as a Service). Microsoft is "all-in" with the cloud.

Does your environment provide you with all three?

Let me know what you think about the key benefits of cloud computing.

Why will it take 30 years for cloud computing to mature?

The problem is that it will take 30 years for cloud computing to reach market maturity. We will need to be patient and plan accordingly; the implication based on technology market cycles is that the real opportunity for cloud services and solutions will be over the next 10-15 years. 

So, why will it take 30 years for cloud computing to reach market maturity?
One reason: cloud computing has a force working against it; that is, well entrenched processes and IT organizations. These organizations, like people, have a survival instinct that is strong. Change can be difficult. Agile organizations  will be better positioned to adopt the cloud and to leap frog others by using it as a competitive advantage. To move even faster.  For the others, it will be easier to use the killer benefit to help eventually overcome their objections.

But the real reason is true for almost any new technology. It takes major technologies about 30 years to fully reach the masses.  Consider the following technologies:
  • Mobile phones: The modern handheld cell phone era began in 1973 when Motorola invented the first cellular portable telephone to be commercialized, known as Motorola DynaTAC 8000X. )
  • Televisions: Now flat panels are going through a market cycle
  • Personal Computers: Some consider the first personal computer to be from 1950 http://www.blinkenlights.com/pc.shtml
  • Internet: The origins of the Internet reach back to the 1960s with both private and United States military research into robust, fault-tolerant, and distributed computer networks)

I realize that the 30 year statement is a bit provocative, but it is practically a law for new technologies. Even if new markets are forced with huge investments, it still takes a lot of time. Laggards have to be almost forced to move. This segment would still opt for rotary dial if it was available. 

Entrepreneurs are at the other end of the spectrum. They often overestimate what is possible in 2-3 years, but underestimate what is possible in 10.  Industry experts and groups like Gartner should factor this law when making some of their predictions.

From my view, we are at the cusp of tremendous growth. I am excited about the next decade with cloud computing. 

One last thing: cloud computing will bring a bit of rain in the form of outages, market contractions, and some drama. It is bound to add to the dialog and excitement. 

What's your view?

What is the killer benefit of cloud computing?

The killer benefit is business continuity. With cloud computing, businesses can improve continuity when faced with real-world events: acquisitions, bankruptcy of a vendor, escrow deals, loss of personnel, moves, growth, and others. This improved continuity helps increase velocity and momentum necessary for growth.

The reason: business continuity is a big deal to investors, stakeholders, and customers. They are the very people that drive these kinds of decisions. It will likely not be the CIO or Director of IT, but a customer that pushes you into the cloud.

Imagine that you are a small to medium-sized business and your biggest customer, a Fortune 50 company, wants to use your solution for their entire company. In this kind of deal, a software escrow agreement will not be enough; they will want your solution to be in the cloud. So that in the event that your company goes under, they can just take ownership. They acquire this virtual property as opposed to trying to figure out a mess of software and hardware that is hard-coded to a particular location with odd configuration and deployment.

Imagine another scenario: a company loses a vast amount of data because of hardware failure and did not notice that their backups had been failing for the past 6 months. Or a RAID 10 system is lost due to administrative error. By the way, evidently most arrays are lost due to human error. There are a ton of other scenarios like these that can hamper business continuity. The result of any one of them can be detrimental.

Cloud computing will also reduce capital and operating expenditures; also, likely to appeal to stakeholders, but business continuity is the killer benefit that will push companies into the cloud.

In my view, cloud computing is great design. What do you think?