Wondering if anyone has used or tested an Aurora DB with a Laravel app? They claim MySQL compatible if using InnoDB and I am literally in the middle of importing data into an instance to test for myself. I have done a bit of googling and keep finding people who were 'going to give it a go' but haven't found anything from anyone ACTUALLY using it.
Interested in thoughts for using it in a production environment and if anyone smarter than me (not hard), can think of reasons why, even if it appears to work right now, there might be future incompatibility issues?
I haven't used it, but knowing AWS and RDS, I suspect it'll be a pretty seamless process.
I'd use Aurora myself if it wasn't more expensive than the MySQL variant. However, I haven't needed the extra power of Aurora in any workload of mine (or at work), so it hasn't been worth trying out yet.
I've got Aurora working with Laravel, however, the instance randomly became read-only after upgrading to the 2 CPU tier. The fix was to delete the "writable" instance and then AWS changed the Read-Only instance that I had been connecting to back to "writable". Not sure if I want to use this in production just yet as that just scared the shit out of me on my dev env.
Thanks for chiming in guys. I also abandoned the idea and opted for a 'boring' old MariaDB RDS instance. Not due to any technical limitation I incurred. Purely from a confidence perspective, and likey the fact I didn't have the time for any potential issues/lessons.
With more time I'd have a proper crack. A very large commercial app we deal with (a vendor of ours) have moved all their services to it (not laravel), and it appears to be working well.
I'm sure someone will jump in here soon with a super positive experience :-)
@cletcher I have run into several optimization problems. Maybe because i don't know how to configure aurora properly. Can you show us proper configuration please.