On our QA environments we are running Debian 9, Keycloak 3.4.3 and Percona “MySQL” XtraDB 5.7.33-36. We have a bunch of backends working fine with XtraDB.
On Production we were running Debian 8 “don’t ask”, and I upgraded Keycloak from 3.2.1 to 3.4.3 last year, and we have a local MySQL 5.5.59 for the Keycloak application. The Keycloak 3.2.1 version didn’t handle primary keys then that is why, they setup that local “old” MySQL 5.5.59 a few years ago. With Keycloak 3.4.3, it uses primary keys, then it can be setup on the Percona XtraDB 18.104.22.168, like we have it on QAs.
I recently upgraded from Debian 8 to Debian 9 our Production servers but on Debian 9 tried to go with MariaDB and the MySQL was not even starting, then I rolled back the virtual machine, and I apt hold to keep the related MySQL packages. Plus, I like a lot Percona productions, I dislike MariaDB… like a lot.
Then now, we are on Debian 9, same Keycloak 3.4.3 and the old MySQL 5.5.59
Then for the database, I was wondering what would be better. The end goal will be to stop using the local MySQL 5.5.59 and move the Keycloak data to our Percona XtraDB “cluster” running v.5.7.33-36 like we have on our QAs environments.
I have read people recommending to upgrade MySQL 5.5.x to 5.6.latest, then 5.6.latest to 5.7. Which if I do, I will be using the Percona MySQL 5.6 and eventually Percona MySQL 5.7. I know once I am on version 5.7 I should be able to grab the data and move into the Percona Xtradb 5.7.33-36 “cluster”.