NewsBits - DB Ransoms, RethinkDB, New Mongoid, Clojure/MongoDB, PostgreSQL internals and more

Published

NewsBits for week ending January 27th: The latest in database ransom news, an update from the RethinkDB community, a fresh Mongoid arrives, Clojure's latest MongoDB driver is for Java too, a look at PostgreSQL's internals, a different way to backup MySQL and Meteor's 2017 plans.

NewsBits is database news, developer news, cloud news and some curiosities from the IT world. It's a big data world out there - let NewsBits be your guide.

Ransoms continue: Emphasising how important it is to make sure your database isn't open to all comers on the web with insecure settings, the latest list of databases which have seen ransomware attacks now reads as MongoDB, Redis, Elasticsearch, Hadoop, Cassandra and CouchDB. Swiss security startup BinaryEdge posted about the signatures seen so far.

A correctly configured database will require authentication, something that's either been never enabled because of bad out-of-the-box defaults trying to make things simple for new users, or something that has been disabled either knowingly or unknowingly (where, for example, security is a pay-for feature which goes away at the end of a trial).

A blog post from the Apache CouchDB project explains what needs to be done to secure current CouchDB databases and promises better defaults for the future. Unsecured Cassandra users may be finding an extra "warning table" in their databases.

RethinkDB Update: The Open RethinkDB community continues to work on maintaining RethinkDB. In the latest update on progress, there's information on future planned releases, including the upcoming release of RethinkDB 2.4. The volunteers are assembling a build and release processes, coordinating contributors and planning a RethinkDB 2.5 release. The plan to acquire and relicense the code has not made much progress, though.

New Mongoid: The MongoDB Ruby ODM Mongoid has been updated for MongoDB 3.4 with the release of Mongoid 6.1.0 and 5.2.0. You'll find the updates on the releases page of the project.

Clojure and MongoDB: A new Clojure client, Monglorious has appeared. The big difference is rather than assembling functions to create queries, this implementation allows you to pass strings like "db.documents.find({ name: 'Xavier' })" to it and it does the work to turn that into a query. Java developers can also use it thanks to a Monglorious-Java wrapper.

PostgreSQL Internals: A new and interesting introduction to the Internals of PostgreSQL has been published by Suzuki Hironobu. Based on his Japanese language book from 2012, the site isn't complete yet as he's in the process of updating and translating particular chapters. If you are in the mood for something more historic, check out Stonebraker and Rowe's paper from 1986.

MySQL Backup: Gopli is a database replication tool for backups written in Go. The developers plan to make it address more databases, but currently, it only handles MySQL. It uses Go's goroutines to power parallel data acquisition. Talking about Go, Go 1.8 is due next week but while you are waiting, why not gopherize yourself.

Meteor and Apollo: The Meteor developers laid out their 2017 plans for the Meteor JavaScript application platform and Apollo GraphQL engine. Although Apollo came about as an exploration of new data mechanisms for Meteor, the developers say they are now completely uncoupled projects and that Meteor will become an Apollo consumer - developers can already consume GraphQL content from it in Meteor, but eventually Apollo could become the core to Meteor's database access.


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.

Image by Ilya Pavlov
Dj Walker-Morgan
Dj Walker-Morgan is Compose's resident Content Curator, and has been both a developer and writer since Apples came in II flavors and Commodores had Pets. Love this article? Head over to Dj Walker-Morgan’s author page to keep reading.

Conquer the Data Layer

Spend your time developing apps, not managing databases.