Running EE on a database cluster? Convert to InnoDB?
How Do I?
Hi all,
What would the recommendation be towards getting EE to run on a database cluster / redundancy system, (in my case I’m using PagodaBox right now) where the traditional pitfall seems to be that EE makes use of FULLTEXT in MyISAM tables, which aren’t supported in InnoDB (I think support is there in the latest bleeding-edge versions of InnoDB).
Has anyone any experience with running EE with redundancy on PagodaBox, or any other PaaS for that matter?
I’ve been Googling all morning and come to no real conclusions, but I’m looking at Engine Yard, Platform.sh and AppFog as possible alternatives at the moment (driven by PagodaBox’s lack of a 24/7 worldwide support and their uptime issues).
Cheers!
I can’t offer too much in terms of suggestions. Although I will say that Amazon RDS is rock solid, but also more difficult than Pagodabox and at times expensive.
It’s definitely safe to run most of EE on InnoDB. As you mentioned FULLTEXT support is the one downfall for getting full InnoDB support, but it looks like Pagodabox supports MySQL 5.6. That said, it will definitely require some tweaking, in the very least in the installer schema to remove the MyISAM restriction on that table.
The bigger problem you’ll run into when using EE in a multi-database environment is that we don’t currently support in-app read/write differentiation. So realistically you’re limited to one connection. Which means no read-only slaves without something like mysql proxy in-between.
If your uptime requirements are critical, then definitely explore master-master replication. If you’re worried about performance, then I would focusing more on caching than on database replication.
Just following up on this item. Is that still the case, that EE does not support multiple connections one for read and another for write? Looking at using that for running it on an AWS Aurora cluster.