This is your weekly summary of Compose news for those changes which may make your life easier. In this edition, the big news is we've opened up in a new region and a look back at recent articles on MongoDB and Redis.
Going "US East" with Compose
Getting your databases as close to your applications or your geographical location is important to us. Making sure you have as many options as possible is equally important. That's why we're pleased to announce that Compose deployments can now be sited in a brand new IBM Cloud public region in Washington DC, or as we like to call it, "US East".
Compose databases can now be located in this region which expands the US coverage of the public IBM Cloud and joins the existing "US South" public region.
Compose database deployments will be distributed over the four data centers that make up the region as part of our standard process for ensuring resilience for your data. As an added benefit, deployments into the "US East" region will automatically be using encryption at rest for data storage.
It's not just Compose.com deployments that can reside on "US East" either. IBM Cloud Compose databases can also make use of the new location which will be the fifth public region listed in the console.
Using US East on Compose
To create a Compose deployment on "US East", go to the Create Deployment menu. Select the database you want to create and in the location menu select "US East 1 (Washington DC)". It's that simple.
If you want to relocate an existing database to US East, use Compose's ability to create a new deployment from a backup. Backup your current database from the Compose console. Then go to that Backup and select the Restore option. You'll be invited to create a new deployment for the restored data to be loaded into; again select "US East 1 (Washington DC)" in the location menu.
Over the last week, we've had articles on MongoDB, Redis and how to write stuff for Compose.
- Keeping data in the admin database of a Compose MongoDB deployment is bad for performance and reliability. We wrote about how to handle the new MongoDB warnings for this problem—specifically, how to tell what's in the admin database, and how to safely get it out of there.
- It's easy to forget about some of the powerful data structures that Redis supports. So we covered some simple examples of how to use Redis sets to handle tagged data to help you make better use of this unheralded feature.
- It's that time of year to write stuff for Compose. In 2018, we're continuing our popular program of inviting experts like you to share your database know-how on our blog, and earn yourself database credits and cash while you're at it.
That's it for this week's Noteworthy at Compose. Until the future!
Read more articles about Compose databases - use our Curated Collections Guide for articles on each database type. If you have any feedback about this or any other Compose article, drop the Compose Articles team a line at firstname.lastname@example.org. We're happy to hear from you.
attribution Casey Horner