Blog Post

Why Run MongoDB on Everpure FlashArray?

,

I’ve spent a lot of years around SQL Server on shared storage, and lately I’ve been spending that time with MongoDB. The database engine couldn’t be more different, but the storage conversation sounds very familiar. How do I protect it? How do I grow it? How do I get another copy of it somewhere else, and how long is all of that going to take?

This is the first post in a series where I run MongoDB replica sets on Everpure FlashArray in my lab, with the commands and the real output in every post. In this post, I’m going to show you why you’d run MongoDB this way at all: what MongoDB asks of storage, where disks inside every node start to hurt, what changes when the volumes come from a FlashArray, and a map of the rest of the series. There’s no lab output in this one, just the reasoning. Let’s go.

Original post (opens in new tab)

Rate

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

You rated this post out of 5. Change rating

Share

Share

Rate

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

You rated this post out of 5. Change rating