Severalnines Blog
The automation and management blog for open source databases

Planets9s - vidaXL choses ClusterControl, scaling & sharding MongoDB & more!

Severalnines
Posted in:

Welcome to this week’s Planets9s, covering all the latest resources and technologies we create around automation and management of open source database infrastructures.

vidaXL choses ClusterControl to manage its MongoDB & MySQL databases

This week we’re happy to announce that we’re helping our customer vidaXL, a global e-commerce platform, compete with eBay and Amazon - and in doing so, keep its tills ringing. In their own words: “Our back-end is reliant on different MySQL & MongoDB databases to tackle different tasks. Using several different tools, rather than a one-stop shop, was detrimental to our productivity. Severalnines’ ClusterControl is that “one-stop shop” and we haven’t looked back. It’s an awesome solution like no other.”

Read the announcement

Live webinar next Tuesday on scaling & sharding MongoDB

Join us on Tuesday next week, November 15th, for this webinar during which we’ll discuss how to plan your MongoDB scaling strategy up front. We’ll cover topics such as what the differences are in read and write scaling with MongoDB, read scaling considerations and read preference will be explained; and we’ll look at how sharding works in MongoDB and at how to scale and shard MongoDB using ClusterControl. “See” you there!

Sign up for the webinar

HA on a Shoestring Budget - Deploying a Minimal Two Node MySQL Galera Cluster

As we regularly get questions on how to set up a Galera cluster with just 2 nodes, we published this hand blog post on why and how to go about that. The general consensus is that users should have at least 3 Galera nodes to avoid network partitioning. Yet there are some valid reasons for considering a 2 node deployment, e.g., if you want to achieve database high availability but have limited budget to spend on a third database node. Or perhaps you are running Galera in a development/sandbox environment and prefer a minimal setup. Whichever the reasoning, here’s a handy quick-guide on how to go about it.

Read the blog

That’s it for this week! Feel free to share these resources with your colleagues and follow us in our social media channels.

Have a good end of the week,

Jean-Jérôme Schmidt
Planets9s Editor
Severalnines AB

Related Post

MySQL on Docker: Composing the Stack

Docker 1.13 introduces a long-awaited feature called Compose-file support. Compose-file defines everything about an application - services, databases, volumes, networks, and dependencies can all be defined in one place.  In this blog, we’ll show you how to use Compose-file to simplify the Docker deployment of MySQL containers.

Posted in:

How to deploy and manage MySQL multi-master replication setups with ClusterControl 1.4

MySQL replication, while simple and popular, may come in different shapes and flavors. Master slave or master master topologies can be configured to suit your environment.  ClusterControl 1.4 brings a list of enhancements to deploy and manage different types of MySQL replication setups. This blog outlines the different topologies that can be deployed, the merits of each topology, and shows how each can be managed in a live environment.

Posted in:

Automatic failover of MySQL Replication - New in ClusterControl 1.4

MySQL replication setups are inevitably related to failovers - what do you do when your master fails and your applications are not able to write to the database anymore? Automated failover is required if you need to quickly recover an environment to keep your database up 24x7. This blog post discusses this new replication feature recently introduced in ClusterControl 1.4.

Posted in:

Automating MySQL Replication with ClusterControl 1.4.0 - what’s new

This blog post will go through new replication features in ClusterControl 1.4.0, including enhanced multi-master deployment, managing replication topology changes, automated failover and handling of replication errors.

Posted in: