Welcome to NewsBits where you'll find the database, cloud, and developer news from around the net for the week ending February 2nd:
- Red Hat acquires etcd creator CoreOS.
- etcd 3.3 released with experimental old API.
- The latest fixes in MongoDB 3.4.11.
- RabbitMQ 3.7.3 polishes up 3.7.
- Elasticsearch gets updates and new .Net client.
- The start of the end of vacuuming for PostgreSQL?
- Rails 5.2rc1 has a Redis Cache and Active Storage
- Projects come to Node-RED 0.18.
- Java 8 gets deferred end of life.
- The end for Node.js 4.x is nigh.
- And finally, Go Space Invaders...
Here are the bits:
Red Hat and CoreOS - The big news of the week was the acquisition of CoreOS by Red Hat. CoreOS, developers of etcd and maker of the Tectonic Kubernetes platform, Quay registry, and Container Linux, will become part of Red Hat's business. Red Hat is emphasizing in an FAQ that CoreOS products will continue to be supported for customers, but it appears most of the CoreOS product line will be subsumed into existing Red Hat open source projects.
etcd 3.3 - The acquisition news didn't stop the latest release of the etcd database. Etcd 3.3 brings an updated BoltDB database from CoreOS's own BoltDB fork, smarter client handling and improved read consistency. There are also some experimental new features, including an etcd v2 API emulator for the etcd v3 storage engine. The ongoing issue is, although the v3 API is relatively simple to implement, it needs a port of gRPC and there are languages like Perl which just don't have one. The v2tov3 emulator looks to bridge that gap and along with the now beta gRPC gateway, ensure more ways to talk with etcd. There are more details in the announcement about performance changes, TLS certificate revocation and wildcard support and all the other changes.
MongoDB 3.4.11 - MongoDB 3.4 gets a three monthly bug fix with MongoDB 3.4.11. The notes for this release highlight a number of server enhancements while the changelog offers details on the nearly 100 fixes in the update.
RabbitMQ 3.7.3 - Another update to the most recent major update of RabbitMQ has arrived in the form of RabbitMQ 3.7.3. The release notes note the authN backend blocking blank passwords as a safety enhancement and a whole range of bug fixes in the core server, management plugin, and CLI tools.
Elastic Updates - Elasticsearch and Kibana both got minor updates this week. Elasticsearch 6.1.3 and 5.6.7 got various bug fixes, while the matching Kibana 6.1.3 and 5.6.7 closed an open redirect issue which only affected users of the proprietary X-Pack security extension and some XSS issues in visualizations. In other news, Elastic announced that NEST and Elasticsearch.Net 6.0 we now generally available; NEST is the high-level .Net client for Elasticsearch while Elasticsearch.Net is the low-level library it uses. There's a lot of changes in this release to give it Elasticsearch 6.x compatibility and improved engineering to make it work better with current .Net practices and trends.
PostgreSQL - Over at EnterpriseDB, Robert Haas has blogged about the possible end of PostgreSQL VACUUM. VACUUM cleans up the MVCC debris created by PostgreSQL's update process and over the years many mitigation strategies have emerged. Read more about that in this Compose Write Stuff article. EnterpriseDB is working to eliminate the VACUUM completely by using what they call a zheap. This is early work and isn't targeted at any PostgreSQL future release yet. It's still good to see someone taking on what has been a fixture of PostgreSQL administration work.
Rails 5.2rc1 - The latest Ruby On Rails, 5.2, has hit release candidate stage. It's got some great new features like Active Storage for managing files in the cloud but the one that interests us the most is the new built-in Redis Cache Store. This is based on work at Basecamp using Redis as a cache extracted into one module with fault tolerance and distributed gets. There's a whole lot more in this release too and the developers are looking to an end of February release.
Node-RED 0.18 - It may look like a small bump in a minor version number but the release of Node-RED 0.18 signals a step on the road to Node-Red 1.0. With 0.18, Projects is the headline feature (and also only a preview) you'll likely want to use. Node-Red can now use Github as a backing store and collaboration space for flows, breaking the old model of "it's just in the local file system". There's also new message sequence nodes for splitting, batching and merging message flows, customizable node icons and more flexible property handling for core nodes. The announcement points out the developers wanted to be closer to 1.0 and are looking for volunteers to join in the efforts to code and document Node-RED, expand the cookbooks or just improve the library of flows.
Java 8 - With Java 9 being a short-term release, Oracle has moved to extend the supported life of Java 8. That means there'll be public updates to Java SE 8 till January 2019 for all, and for personal users, updates till the end of 2020. Java 9 will see its public updates end in March. Java 10 is due around there and it will have a short lifetime, with updates ending in September 2018 when Java 11 should arrive as a new long-term supported edition with a likely five-year lifespan. More details in Oracle's support roadmap.
Node.js - PSA: If you still have Node.js version 4 in use, remember it reaches its end of life on the 30th April this year and you should be looking to at least upgrade to 6.x. Timings from the Node.js release schedule.
And finally, a little bit of Space Invaders. Specifically, Sau Sheong Chang's experiment in writing a Space Invaders in Go with no supporting framework. It works by exploiting a rarely used inline graphics feature in iTerm2 for macOS and the article talks through how the sprites and collision physics were created.
NewsBits. News in bits, every Friday 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 firstname.lastname@example.org. We're happy to hear from you.