We're giving users more control on how they can view their many databases on Compose - and it all started with us adding a new field. We've also added a safety catch to the Compose delete database UI and there's a small Redis update too. Find out more...
New ways to view your databases
Some weeks back we mentioned that we'd added a new field, "Billing Code" to the additional information you could add to your Compose database deployments.
This was originally planned as a field for Compose users with some very specialized problems, but we realized that it could also be a very useful feature for everyone, so we made sure everyone could see and set the field on their databases.
Now, we are following through. We have just turned on the first user-visible feature to use that field: a new Group By option which gives you new views on your Compose databases.
When you pull up the Deployments view, over on the right at the top of the listing, the Group By selector offers three options: Tenancy, Billing Code and Datacenter.
The first option, Tenancy, is designed for any Compose user who has an Enterprise deployment. It sorts the databases into groups by the Compose Enterprise clusters they reside on. Databases that are hosted on Compose's multi-tenant service show up under Compose Hosted. That's the default view.
If you've set billing codes on your database deployments, then you can select Billing Code in your Group By button.
The databases will be gathered up according to that field. In the screenshot above, two databases have the billing code "Demo101" so they are grouped. If you haven't set the field for them, they'll be gathered up under a (no billing code) group. So now, if you supply your services and Compose databases to various clients, you too can set a billing code for your clients and, by simply setting the grouping option, get to see which clients have which databases.
Finally, there's the Datacenter view. A "Datacenter" here is an amalgam of cloud platform and region and incorporates all the Compose infrastructure deployed across availability zones, racks or other high availability configuration. What that means to you is a quick way to refer to where your databases (or enterprise clusters) reside. When you select Datacenter you'll see something like this:
Now the list is grouped by the Datacenters in alphabetical order. If a deployment is in an Enterprise cluster that operates from that location, the clusters name will appear on the right-hand side of the row too.
Put together, the new options give you three useful ways to see your databases in geographic, logistical or financial context.
Safer database deletion
We considered how, even after prompting for a password, it was relatively easy to delete a database deployment. Once authenticated, it just required the button to be selected. So, we've added a safety catch to the process that looks like this:
If you haven't authenticated recently, you will need to click the Authenticate before Deleting button and enter your password first. After that, or if you had already authenticated you'll see this:
The difference now is that you can enter the deployment name into the field as an active step to confirm you want to delete this deployment. When you are done, click Delete Deployment and the database will be but a memory.
Finally, in this Compose Notes, we've made Redis 3.2.9 available. Users of Redis 3.2.6 or earlier should visit the Compose console for their Redis deployment where they will be prompted to upgrade. The upgrade mostly consists of minor fixes, by moving from 3.2.6 to 3.2.9, users will be skipping the versions which had issues with the memory allocation library.