Trying to figure out which cloud service provider to choose for your cloud database migration? When switching from a commercial, on-premise database over to open source with either public or private cloud there are a number of cloud database migration options available.
Most cloud providers offer DBaaS across many of the common open source database engines such as MySQL, PostgreSQL, and MariaDB, plus non-relational databases like MongoDB and Redis. While creating, running, and managing a database with each cloud provider may be easy, migration takes a little more patience and setup.
We take a deeper look into migrating from commercial engines to AWS, Azure, and Google Cloud for open source database storage and operations – along with considerations for deploying to your own on premise private cloud environment.
Database migration can be a clever move – provided you review your current system, then choose the correct database type and provider to migrate to.
The capabilities of open source relational database management systems have increased dramatically over the past few years. Innovative uses for large, web scale, applications has helped drive this along with many of these database platforms underpinning public cloud DBaaS offerings.
Organisations looking to drive up innovation along with maintaining or lowering capex and operational cost now have many database platform options available. PostgreSQL, AWS Aurora and AWS RDS offerings all provide robust relational database management platforms.
What does this mean however for your existing commercial RDBMS platforms? Are the open source database platforms a new trend with limited lifespan? What are the specific use cases where organisations should consider migrating their commercial database to an open source database?
Database security is crucial to protecting an organisations data assets. We cover some practical approaches to increasing your data security by hardening your database management systems.
Data security consistently remains one of the top priorities for CIO’s. Increasing threats combined with increasing regulatory and compliance requirements means this is unlikely to change in the foreseeable future.
Securing your enterprise database estate through database hardening provides a robust way to ensure the policies designed to protect the organisation’s data are implemented directly on the database itself.
Why is it then that database hardening remains an uncommon practice across organisations?
Hosting an organisation’s applications and databases in a public cloud service can offer significant overall cost and efficiency benefits. As part of the process of moving to the new services you need to quantify cloud migration costs: both one-off and ongoing
Ongoing operational costs post-migration can be well understood and estimated in advance. There are public cloud service cost estimation tools (Oracle Cloud Cost Estimator, AWS Simple Monthly Calculator), or you can lock-in your service costs via agreed subscriptions.
In this blog, I will discuss some of the additional costs to be aware of when migrating applications and databases to a public cloud.
A well-executed cloud migration project starts with migrating data to a cloud platform. The quickest and easiest way to do this is by using existing database backup technologies to write backups to cloud storage.
The ideal scenario is to execute a cloud strategy with minimal risk and change to your existing critical systems. Therefore, setting up a cloud-based DR environment isn’t ideal as a first step.
A DR environment automatically commissions the cloud environment as part of the production landscape with the associated operational requirements.
This introduces additional dependencies at the early stage of your cloud journey that your business may not be ready to commit to yet.
Moving your data to the cloud may seem like a necessity. But there are cloud migration considerations you need to factor into your business case for such a major project.
As a consultant in the area, I have come across many cases where clients believe the migration of mission-critical data to the cloud is a requirement. But in my experience, there are instances where staying on-premise is just as valid, if not preferable.
Moving mission-critical data from on-premise servers to the cloud is a major undertaking which may deter a business from making the move. But there are costs associated with keeping your data on-premise which you need to consider. This includes the possibility that the cost benefits of cloud services could significantly outweigh the negative costs of the cloud migration itself.
Knowing the cloud migration benefits is important as making the decision to move your mission-critical database to the cloud is not a decision to be taken lightly.
There are many factors you need to consider and choices you need to make. However, the first task is to build a cost/benefit analysis of a cloud migration business case for executive management to consider.
In this blog post, I will discuss the tangible cloud migration benefits. Many of which you should consider referencing in your business case.
Cloud services are a key component of every IT cloud migration. Depending on your objectives and requirements, different cloud service providers should be evaluated to ensure the best fit for your purpose.
Here I compare each of the major cloud service providers and evaluate their core offerings. Given the vast differences in customer requirements it’s impossible to provide specific recommendations – but I do outline the pros and cons of each service.