Glad You're Ready. Let's Get Started!

Let us know how we can contact you.

Thank you!

We'll respond shortly.

Standup SF 09/06/12: Clusters are clusters


  • Recommended MySQL master-slave gem?

We want to set up our database in a master-slave setup and would like to know what gem is currently recommended.

Answer according to Palermo: Don’t use MySQL master-slave

  • Experiences running Redis in Master/Slave setup?

Our client wants to run Redis with a Master/Slave setup. Has anyone ever done this? What experiences did you make?

Answer according to Davis:
There are 2 options, Redis Cluster which is complete vaporware and Redis Sentinel which is recently released. TLDR: Redis Sentinel


  • Google offers MySQL cloudy cloud

MySQL in the Google Cloud – Now you can use Google App Engine without being stuck with a key-value data store.

  1. Joseph Palermo says:

    The main reason I have for not doing a read slave is the problem of replication lag. This is where your read slave is behind your master by seconds or even minutes.

    Once this happens (and it will once you get under load), you start to get weird bugs. Create something, and redirect the user back to the index page… and they can’t see the thing they just created.

    You’ll spend a lot of developer time, and thus money, solving this problem. The best solution is a write through cache, like cache-money. The only problem is that has been abandoned, and there are over 100 forks of it.

    Even if you find a version of it that works for you, it still takes some time to implement it and there are edge cases it does not solve that you’ll need to watch for.

    It is far cheaper to just buy a bigger database. A beefy server with solid state drives will take you a VERY long way.

Post a Comment

Your Information (Name required. Email address will not be displayed with comment.)

* Copy This Password *

* Type Or Paste Password Here *