Support: 1-800-961-4454
Sales Chat
The container-based virtualization architecture we use in Rackspace’s Cloud Databases service has a number of benefits, one of which is a reduction in the overhead that is typical of traditional virtualization. Less overhead means more CPU for your compute-intensive databases.
Last week, we showed you a short video on the API for Cloud Databases. Today, we want to show you another short video from a couple of Rackers on the team that highlights some of the different use cases for Cloud Databases that we have seen customers using. Take a look. Do you have a different use case for Cloud Databases? Leave a comment here and let us know.
Using the Cloud Control Panel to manage your Cloud Databases is great for scenarios where your application has only a few databases or you don’t have a lot of automation needs. But what if you are responsible for tens or hundreds of databases? Maybe it’s because you manage them on behalf of your customers or offer services on top of Cloud Databases. In that case, using the Cloud Databases API is almost a requirement.
One of the advantages of the container-based virtualization architecture we use in Rackspace’s Cloud Databases service is the improved IO performance for your database. This performance improvement is primarily due to two reasons: the elimination of the hypervisor as a “middleman” in the path that goes from the database engine to the storage; and the flexibility in IO priority allocation that Cloud Databases gives to each one of the different containers of the system.
A few days ago we told you about the Unlimited Availability of Cloud Databases. Since then, we have talked with many of you about what you like about Cloud Databases and what you would like to see added. One thing that we consistently hear about from current users is the different levels of support we offer for databases based on whether your account is a Core Cloud account or an Account with a Managed Service Level.
Racker Powered
©2016 Rackspace, US Inc.