Your weekly summary of Compose has a rundown of the most recent database articles published and news of those small changes which may make your life easier.

Compose Articles

This week we looked at Scylla and simpler Cql with Go, securing notebooks and more PostgreSQL tools:

• In Go and simplifying Scylla with Gocqlx we introduce you to Gocqlx which makes life a lot easier when pushing and pulling data in and out of a Scylla database/

• Notebooks make doing science with data easy to do and present, but so easy you may forget to not expose the databases you are pulling data from. We look at this problem in Securing Notebooks on IBM's Data Science Experience and offer some easy solutions.

• In our ongoing quest to plug every tool we can into Compose databases, this week in ToolUp, we looked at PostgreSQL Studio 2.0, a web interface for interacting and developing with PostgreSQL.

Noteworthy Changes

Noteworthy changes this week include a new password update API endpoint, new filters for recipes and refined backups for Elasticsearch.

• Passwords: We quietly released a new endpoint a few weeks ago that lets API users change the password on their deployments. Use with care as this can trigger a rolling restart depending on the database type having its password changed. The endpoint will return a recipe to keep you informed of its progress.

• Recipes: If you don't know, a recipe is what Compose runs on a deployment to change settings, add portals, scale or well, anything to do with administering it. That's where we've made another changed. You can ask a Compose deployment for a list of all the recipes that have been run against it through our get deployment recipes API endpoint. But for a long lived deployment, that can mean a lot of data, much of it probably irrelevant. To help you and your API app focus, we've added limit to restrict the number of recipes returned and status to filter returned recipes so only particular statuses are returned.

• Elasticsearch Backups: We’ve been doing that extra bit of engineering that you’d expect from Compose and although you won’t see it, there’s a chance you’ll feel this change. We’re just moving Elasticsearch backups to a smoother, performance-friendlier incremental backup.

That's it for this week's Noteworthy at Compose.

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 articles@compose.com. We're happy to hear from you.

attribution Jan Kahánek