As you probably know, WhereScape RED is fully cloud-ready. However, owing to the differences in configuration that you’re going to experience when dealing with cloud infrastructure versus your own data centre, there are some differences in how you’ll work with WhereScape RED in the cloud.
The biggest point before we go any further is that WhereScape RED in the cloud is very similar to WhereScape RED on-premises. This is by design for these reasons:
We want to provide you with familiar development environment
We don’t want you to undergo major re-building of skillsets.
We want to provide you with a migration path that is as seamless as possible.
It is a case of knowing where the differences are so you can get going, be productive, and take advantage of your new cloud platform as quickly as possible.
There are major advantages to companies moving from a WhereScape RED data warehouse on-premises to a WhereScape RED data warehouse in the cloud:
- It is a pretty straightforward process. It doesn’t take long and there is a minimum of rewriting involved. It is a conversion process, not a re-doing of something already done. You don’t have to reinvent the wheel, or even worse, rebuild the entire data warehouse (something which could take years).
- All your logic, data warehouse structures and everything else migrate into the cloud too.
- In an earlier blog, we’ve discussed the merits of ELT over the increasingly outdated approach of ETL; in the cloud, RED still does just this, harnessing and centralising data processing and computing within the database platform itself. This means you don’t need to waste time and money on setting up a discrete ETL engine; the database platform itself has the smarts to manage computing demand, scale-up and scale-out.
What’s more, WhereScape RED supports all the major cloud database platforms.
So what are the differences to on-premises?
To facilitate multi-platform compatibility, the following enhancements have been made:
Code generation is decoupled from the software engine itself. In the on-premises version, it was embedded. Now it’s done through the use of templates.
The data warehouse data is separated from the metadata, and RED now supports writing data warehouse data to multiple locations (in the cloud – you might be using several different platforms, e.g. writing to a data lake as well as to a database). This is called Custom Targets.
RED now supports database platforms that don’t support database procedures, this is essential to support the diverse range of database PaaS available today.
More on those templates
I’ve mentioned that code is generated through templates and it is worth going into this in a little more detail. The concept is the same as the templates you’ll find in Microsoft Word, except in RED they are scripting language templates which provide code outlines for generating full SQL blocks or PowerShell scripts relevant to the database platforms, the objects, and the operations that the templates are applied to.
There are multiple templates already available and supplied to clients to perform most standard operations, these will help you get just about everything you need done. If you have customised requirements, it’s quite possible to get stuck in, learn the template language, and modify or develop new templates. There is a little bit of a learning curve to get up to speed on the templates, but it isn’t steep. Or you can discuss it with us and we’ll work with you to address your specific requirements.
There are templates for all the major PaaS vendors: Snowflake, AWS Redshift, Azure SQL DB, Azure SQL DW, we also have templates for exporting data to and reading from Blob Storage. Templates for other platforms are being developed and where there is demand for any new ones, well, we’ll get on to that too.
Templates strengthen a benefit of RED: flexibility. We can modify details of database operations performed by RED or cater for new / specific database operation requirements.
The WhereScape engineers have worked hard to make sure RED users have a simple, fast and flexible route to cloud that doesn’t require you to completely re-skill your data team.
If you’re keen to explore the possibilities, give us a shout. We’re happy to explain more, provide an assessment, and support your cloud migration process.