Everyone is thinking about migrating to the cloud but before you can make the move we should look at whether cloud migration is a viable option for the business and how to make the same with zero to least business disruption:
A company should be looking at cloud database option if:
- The ability to manage databases in-house is inadequate or expensive
- IT is not a central functional unit
- You need to cut initial Capex expenses
- You are working with new applications or developing one, and want to try the cloud as a testing environment
- Moving to the cloud for your disaster recovery (DR) backup, and using it as a trial run to identify issues and hurdles to database migration
One fact circulated last month at Teradata Partners was that 90 percent of Teradata customers believe they will be on some form of hybrid cloud by 2020 and 40 percent of workloads will be run there.
In the past, the only clear choice for most organizations was on-premises data — oftentimes using an appliance-based platform. However, the costs of scale are gnawing away at the notion that this remains the best approach for all (or even some) of a company’s analytical needs.
4 Factors Leading to More Cloud Databases
A greater comfort with cloud deployment is emerging. Businesses that are migrating databases to the cloud or building databases there are usually doing so as a result of one of these factors.
1: Scaling the Appliance Model Has a High Cost
Though appliances bring power and familiarity, the business case to scale up with additional appliances (for example, to expand storage, analytics workload capacity, or disaster recovery) is sometimes difficult to sell based on its finances. Cost goes beyond the purchase price to include maintenance, real estate needed, and necessary in-house talent.
2: The Cloud Is Becoming the “Center of Gravity”
Companies are sharing and accessing data in the cloud at an unprecedented pace. Organizations that are pulling data down from the cloud, integrating it, transforming it, and storing it on premises are moving the heavier data load to the analytics, rather than the preferred model of moving the analytics to the data.
3: On-Premise Databases Are Reaching Capacity
The dreaded expansion conversation these days quickly considers the cloud. Non-functional requirements (NFRs) such as the separation between development and testing, QA and production, and disaster recovery are being ruggedized and modernized and this means additional environments. The cloud is finding a strong value proposition in supporting NFRs.
4: Emerging Use Cases Are Specific to Cloud
There are many emerging technical use cases that are exclusive to the cloud model. Separating compute nodes from storage nodes allows you to independently scale compute and storage in the likely event you need more of one than the other. Immediate elasticity gives you maximum flexibility and serenity as your workloads grow and shrink seamlessly.
Considering these factors (and potentially others), organizations are turning to the cloud — some stepwise and some en masse — to mitigate the challenges they face managing and maintaining an expanding data ecosystem.
Considering Full-Cloud, Secondary-Cloud, and Hybrid-Cloud Deployments
Many enterprises are fully embracing a cloud-based enterprise data warehouse and making it accessible across their current infrastructure and data ecosystems. Many others are adopting the cloud as a secondary platform for a specific purpose such as disaster recovery. An active secondary platform also serves as an accessible backup system should it be needed.
Some organizations have already moved to cloud-based solutions of various scales and varieties. Others are taking a stepwise approach and pivoting components of their architecture to accommodate the cloud, thereby creating a modern, cost-effective, and scalable hybrid architecture.
Either way, the cloud’s price/performance value proposition is now very strong for databases and should be given priority consideration for new or renewed data efforts. Don’t let the lack of an enterprise cloud strategy be a barrier. Start it with the data. Start it with you. Start it with OrbIT !