How to trace the history of MySQL data
If you provide an API service that integrates multiple underlying systems, which are out of your control, you’ll be the first person that gets blamed when an error occurs. As a result, you have to quickly identify where the error originated. Do you have a bug in your application? Is the bug in some other system you use? Which one?
Josef and Artyom used to ask themselves the same questions and debugging these data problems was a nightmare. It took weeks to find out how the incorrect data sneaked into their API. They wanted to stop these issues once and for all.
So, they designed and developed a solution that made it possible to investigate suspicious data in a matter of minutes. But wait, there’s more. They can also update their cache as soon as the data changes in the database. Consequently, Livesport’s “Sport API” is extremely reliable, which is very important for clients who want them to deliver the correct data as fast as possible. Josef and Artyom will show you how they did it using multiple technologies like Maxwell, MongoDb, Redis, and more.
Full-stack Developer @ Livesport
Josef is a full stack developer who likes backend API development in TypeScript and PHP as well as React on frontend. He’s responsible for building services for Livesport's API ecosystem to deliver data super fast. He loves modern technologies and tries to apply them wherever possible. On top of that, he develops some personal side projects, such as smsbot.cz.
Node.js Developer @ Livesport
Artyom is a backend software developer working in a team whose goal is to create the world’s fastest “Sport API” for Livesport. He has a lot of experience with automation, tools, and library creation to make the lives of programmers easier.
Artyom has a passion for problem-solving and is also fascinated by data flow and performance optimization. He writes mostly in Node.js with TypeScript and tries to write programs for everything that he needs to do manually more than once.