We wish we could tell you that there are clear distinctions between private and public clouds. Unfortunately, the lines are blurring between these two approaches. Hybrid approaches also are starting to take hold. For example, some public cloud companies are now offering private versions of their public clouds. Some companies that only offered private cloud technologies are now offering public versions of those same capabilities. In this section we offer some issues to consider when you’re making your business decision.
Going public
When is a public cloud the obvious choice? Here are some examples:
✓ Your standardized workload for applications is used by lots of people. Email is an excellent example.
✓ You need to test and develop application code.
✓ You have SaaS (Software as a Service) applications from a vendor who has a well-implemented security strategy.
✓ You need incremental capacity (to add compute capacity for peak times).
✓ You’re doing collaboration projects.
✓ You’re doing an ad-hoc software development project using a Platform as a Service (PaaS) offering.
Many IT department executives are concerned about public cloud security and reliability. You need to get security right and handle any legal and governance issues, or the short-term cost savings could turn into a long-term nightmare.
Keeping things private
In contrast, when would a private cloud be the obvious choice? Here are some examples:
✓ Your business is your data and your applications. Therefore, control and security are paramount.
✓ Your business is part of an industry that must conform to strict security and data privacy issues. A private cloud will meet those requirements.
✓ Your company is large enough that you have the economies of scale to run a next generation cloud data center efficiently and effectively.
Driving a hybrid
Now add one more choice into the mix: the hybrid cloud. When would you use it? It isn’t about making an either/or choice between a public or private cloud. In most situations, we think a hybrid environment will satisfy many business needs. Here are a few examples:
✓ Your company likes a SaaS application and wants to use it as a standard throughout the company; you’re concerned about security. To solve this problem, your SaaS vendor creates a private cloud just for your company inside their firewall. They provide you with a virtual private network (VPN) for additional security. Now you have both public and private cloud ingredients.
✓ Your company offers services that are tailored for different vertical markets. For example, you might offer to handle claims payments for insurance agents, shipping services for manufacturers, or credit checking services for local banks. You may want to use a public cloud to create an online environment so each of your customers can send you requests and review their account status. However, you might want to keep the data that you manage for these customers within your own private cloud.
Although private and public cloud environments each have management requirements by themselves, these requirements become much more complex when you need to manage private, public, and traditional data centers all together. You need to add capabilities for federating (linking distributed resources) these environments. In addition, your service levels need to focus on how a service is working rather than how a server is working.
Source of Information : cloud computing for dummies 2010 retail ebook distribution
Going public
When is a public cloud the obvious choice? Here are some examples:
✓ Your standardized workload for applications is used by lots of people. Email is an excellent example.
✓ You need to test and develop application code.
✓ You have SaaS (Software as a Service) applications from a vendor who has a well-implemented security strategy.
✓ You need incremental capacity (to add compute capacity for peak times).
✓ You’re doing collaboration projects.
✓ You’re doing an ad-hoc software development project using a Platform as a Service (PaaS) offering.
Many IT department executives are concerned about public cloud security and reliability. You need to get security right and handle any legal and governance issues, or the short-term cost savings could turn into a long-term nightmare.
Keeping things private
In contrast, when would a private cloud be the obvious choice? Here are some examples:
✓ Your business is your data and your applications. Therefore, control and security are paramount.
✓ Your business is part of an industry that must conform to strict security and data privacy issues. A private cloud will meet those requirements.
✓ Your company is large enough that you have the economies of scale to run a next generation cloud data center efficiently and effectively.
Driving a hybrid
Now add one more choice into the mix: the hybrid cloud. When would you use it? It isn’t about making an either/or choice between a public or private cloud. In most situations, we think a hybrid environment will satisfy many business needs. Here are a few examples:
✓ Your company likes a SaaS application and wants to use it as a standard throughout the company; you’re concerned about security. To solve this problem, your SaaS vendor creates a private cloud just for your company inside their firewall. They provide you with a virtual private network (VPN) for additional security. Now you have both public and private cloud ingredients.
✓ Your company offers services that are tailored for different vertical markets. For example, you might offer to handle claims payments for insurance agents, shipping services for manufacturers, or credit checking services for local banks. You may want to use a public cloud to create an online environment so each of your customers can send you requests and review their account status. However, you might want to keep the data that you manage for these customers within your own private cloud.
Although private and public cloud environments each have management requirements by themselves, these requirements become much more complex when you need to manage private, public, and traditional data centers all together. You need to add capabilities for federating (linking distributed resources) these environments. In addition, your service levels need to focus on how a service is working rather than how a server is working.
Source of Information : cloud computing for dummies 2010 retail ebook distribution
|
|
0 comments
Post a Comment