Database isolation: how we deal with hundreds of direct connections to the database [ukr]
What can go wrong if you allow each service to access the database directly? In a startup, this seems like a quick and easy solution, but as the system scales, problems appear that no one could have guessed.
In my talk, I'll share Solidgate's experience in transforming its architecture: from the chaos of direct connections to a service-based data access model. I will talk about the transition stages, bottlenecks, and how isolation affected infrastructure support. I will honestly show what worked and what didn't. In short, we will analyze the controversy of this talk.
Mykhailo Kratiuk
Backend Software Engineer at Solidgate
- He worked his way up from an intern at a startup to an out-staff Platform Software Engineer at Atlassian. Later, he became interested in Ukrainian fintech and joined the Core Team at Solidgate
- Over 4 years of experience in developing cloud and self-hosted products for the global market
- Believes that high-load systems are one of the best places for professional development of an engineer, as it is here that the high cost of an error, equally high reliability requirements and quick feedback on the decisions made are combined