"Editor's note" for businesses, the autonomy, agility, and productivity of cloud services are the main criteria they choose, and it is highly efficient to cater to their needs through the operation of private clouds. The technology management team should be committed to maximizing the value of private cloud to serve the market, and Forreste introduces the 10 facts of the private cloud, enabling the technology management leadership and management team to better deploy private cloud strategies.
The following is the translation:
Cloud is a key part of every enterprise in employee and customer technology management strategies today, but it is not easy to design robust cloud strategies for filtering market noise.
Perhaps developers and business leaders will not choose a public cloud because they are more focused on the autonomy, agility, and productivity of cloud services than the price of cloud services, so how do you get a private cloud to be more efficient?
Yes, a private cloud has many benefits (for example, scalability, cost savings, and support for developers). However, not all cloud deployment types and strategies support attributes. Why do businesses have to tangle with private clouds?
The technology management team must become a reliable cloud service provider and adjust their business perspectives to free market consumers. This conversion is not easy. The natural trend of the in-house Technology management team is resource optimization and cost-saving priorities, rather than the cloud as a new technology that drives business success.
Before your private cloud strategy, it is recommended that all technical management leaders and teams familiarize themselves with the following 10 truths about the private cloud to better focus the team's efforts on maximizing the value of the private cloud.
Fact 1: Cloud concept abuse, are you that cloud?
A cloud-labeled environment does not mean that cloud value can be delivered. The report shows that 29% of North American and European companies adopt private clouds, but Forrester finds real adoption rates low, with only a handful of companies applying 3 core components of a private cloud environment: Self service access, tracking and monitoring resources, and full automation.
Fact 2: Private cloud Tags can be applied to a range of
Based on research, interviews and telephone calls, Forrester discovered the rise of four of private cloud methods, which used a very different strategy and therefore had different scope and output. Each strategy reflects different priorities, budgets, sizes, key successes, vendor selection criteria, and adjustments. These four types are: Enhanced virtualization, testing, development cloud (as instructed by it), Public cloud Lite and conversion cloud.
Fact 3: Operational efficiency is good, but developer support is better
Much of the investment in technology management over the past 10 years has focused on improving the efficiency of technology management operations, but today's leading companies have focused their attention on business, making them unique in their competition through new technologies.
Fact 4: Transition mixed cloud strategy moves slowly
Repairing the old, calibrating the new is not easy--doing both things at the same time may be a difficult process to tolerate. Can your developers wait that long? While it is slow to adopt a transformational approach that targets all existing visualization resources, it can be a strong long-term strategy. Despite long-term benefit objectives, it is important to provide dynamic resources for products and marketing groups in the short term.
Fact 5: The most time-consuming steps: integration and process automation
New resources do not delay private cloud adoption, but connecting these environments to your recording systems, operating processes, and workbench systems can delay cloud adoption. Finding the right minimum level of external integration and operational support helps you initialize the cloud. And then further integration based on the requirements plan.
Fact 6: An environment is not suitable for all workloads
Businesses no longer regard public and private clouds as either or both. Specific application features are associated with a specific deployment model, and the enterprise begins to weigh the public and private clouds against the application/workload level. The leading enterprise goes further and pursues the application-resource strategy optimization for the entire internal and external deployment.
Fact 7: The cloud economy is tied to the public cloud, not the private cloud
Cloud-related cost-saving commitments are based on a particular user situation and are largely related to the public cloud rather than the private cloud. The private cloud environment requires a large, different use base, a high standard of cost, a universal fallback system, active capacity planning and integration practices. Because of policies and processes, many companies cannot achieve this.
Fact 8: Without tracking employee efficiency, private cloud ROI is a hassle
The ROI of a private cloud is not clear, nor should it be the most important criterion of achievement. A large number of case studies claim that private clouds are hard to save costs. These studies count virtualization and consolidation savings as total savings, and this does not mean that many mature companies.
Fact 9: Private cloud must begin with organizational structure and effective incentives
Change is not easy, especially if it means less perceived relevance or changes in the impact of responsibilities (because their skills are no longer needed). Automation, external sourcing and cloud are all likely to lead to changes in infrastructure, operations, and security teams. Designing and implementing incentive change rewards while demonstrating exciting career paths is key to a successful private cloud strategy.
Fact 10:paas or IaaS
The foundation of any private cloud is to provide a virtual infrastructure as a service (IaaS). But many corporate infrastructure & operations leaders want to provide a more complete development environment or use a private cloud to enhance the enterprise's architectural standards. As a result, they often say they want a platform as a service (PaaS), not just IaaS. But do you really need a PAAs? The fact is that you may need to mix the two, taking the public cloud as an example, IaaS and PAAs are converging.
Original link: forrester:top Facts about private Cloud (translation/Renjun Zebian/Zhonghao)
Free Subscription "CSDN cloud Computing (left) and csdn large data (right)" micro-letter public number, real-time grasp of first-hand cloud news, to understand the latest big data progress!
CSDN publishes related cloud computing information, such as virtualization, Docker, OpenStack, Cloudstack, and data centers, sharing Hadoop, Spark, Nosql/newsql, HBase, Impala, memory calculations, stream computing, Machine learning and intelligent algorithms and other related large data views, providing cloud computing and large data technology, platform, practice and industry information services.