MySQL looks like the wrong choice of database for your application anyways as it doesn't really scale. And if you use the real cloud services (key-value store, file store, ...) it wouldn't be easy to switch between two clouds.
We know that MySQL is a wrong choice for our product, but what started as an experiment is now a real product used by millions of devices. We are moving away from MySQL for the log storage that's what it requires more work on the database storage engine.
But this change requires some time and meanwhile, you need to keep the service running, so having a better SQL server will release stress on the team.
Reminds me of this youtube.com/watch?v=b2F-DItXtZs
I'm not saying stick with MySQL, but I would say you've probably got a better idea what your app needs and wants, and you should be in control of tech-stack, which it seems you are moving towards enabling you to make changes when as a business you've tested and know it's right.
Correct, we're still keeping MySQL for some things but moving to Elasticsearch for log data. We're using each tool for what they're good at.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.