Compose for MongoDB upgrade - Noteworthy at Compose


This is your weekly summary of Compose news for those changes and updates which can make your life easier. In this November 5th, 2018 edition, we look at upgrading Compose for MongoDB to 3.6.8 and we also cover last week's Compose Articles.

At the end of last week, we released Compose for MongoDB version 3.6.8 for all customers.

Existing Compose for MongoDB customers can upgrade their database in place by clicking on the Settings option in their Compose console and then click on the Change Version button.

Customers also can create a backup of their Compose for MongoDB database and restore it into a new deployment running version 3.6.8.

Compose for MongoDB version 3.4.10 will continue to be the preferred version for the next 30 days, starting from November 2nd, 2018. After that, version 3.6.8 will become the default, preferred version. So we recommend that all users running version 3.4.10 upgrade to the latest major version 3.6.8 on Compose.

Compose Articles

We didn't have any new articles out last week, but we wanted to go over last week's Noteworthy at Compose. We had an update to the Compose API for PostgreSQL deployments. Now, users can use the API to increase their PostgreSQL connection limits using the /max_connections endpoint. We recommend that you look into using a connection pooling middleware or PostgreSQL driver that uses connection pooling first, however, just to see if that improves your performance before having to scale up your database.

We had an interesting NewsBits as well last week. TimescaleDB announced version 1.0 and Fedora 29 was released. Read about those and other bits over there.

That's it for this week's Noteworthy at Compose. Onward to next week!

Abdullah Alger
Abdullah Alger is a former University lecturer who likes to dig into code, show people how to use and abuse technology, talk about GIS, and fish when the conditions are right. Coffee is in his DNA. Love this article? Head over to Abdullah Alger’s author page to keep reading.

Conquer the Data Layer

Spend your time developing apps, not managing databases.