Choosing data stores for your business use case

Abstract:

MySQL’s “utf8” encoding only supports three bytes per character. The real UTF-8 encoding needs up to four bytes per character. After upgrading our app’s rails version in production, we started noticing issues in saving objects in the database because of MySQL’s strict mode. We’ll talk about key learnings, the migration itself and best practises for newer apps.

Target Audience:

Developers/Devops Engineers

Outline

1. How we supported storing utf8 content in our app.
2. How upgrading the rails version caused MySQL to run in strict mode causing the problems.
3. How we evaluated our options and chose the final solution.
4. The actual migration and dealing with ad-hoc issues.

Requirements

None

Speaker bio

Lead Software Engineer @ Freshworks.

Links

• https://drive.google.com/file/d/1xmf55SDQijHKpqsBIjhMvKsiXDbM-QGf/view?usp=sharing