An under advertised feature of MongoDB is its ability to compress data between the client and the server. This blog will show you exactly how to enable network compression along with a script you can run to see concrete results. Not only will you save some $, but your performance will also likely improve - a true win-win.


MongoDB Network Compression: A Win-Win

One of Atlas' many great features is that it provides you the ability to pause clusters that are not currently needed, which primarily includes non-prod environments. This article shows you how to automatically pause clusters that go unused for a any period of time that you desire.

Auto Pausing Inactive Clusters

We'll do the hard stuff the easy way by starting only with data and building out an entire site using GraphQL.

GraphQL: The Easy Way to Do the Hard Stuff

If you're interested in how to integrate MongoDB eventing with Socket.io, this tutorial builds in the Socket.IO getting started guide to incorporate MongoDB.

Integrating MongoDB Change Streams with Socket.IO

In this article I will show you how a Scheduled Trigger can be used to easily incorporate automation into your environment. In addition to pausing and unpausing a cluster, I’ll similarly show how cluster scale up and down events could also be placed on a schedule. Both of these activities allow you to save on costs for when you either don’t need the cluster (paused), or don’t need it to support peak workloads (scale down).

Brian Leonard

Content by Brian Leonard

MongoDB Network Compression: A Win-Win

Auto Pausing Inactive Clusters

GraphQL: The Easy Way to Do the Hard Stuff

Integrating MongoDB Change Streams with Socket.IO

Atlas Cluster Automation Using Scheduled Triggers