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),In this presentation I will try to analyze the experience of using pgbouncer and other database proxies at prom.ua. What profit does it bring in organizational sense, what new flexibility it gives to the infrastructure and everyday maintenance and scaling, which additional enchancements we managed to implement and test, what worked and what did not.
Vitaliy Kharytonskiy
(Solution Architect, Prom.ua),In this presentation I will try to analyze the experience of using pgbouncer and other database proxies at prom.ua. What profit does it bring in organizational sense, what new flexibility it gives to the infrastructure and everyday maintenance and scaling, which additional enchancements we managed to implement and test, what worked and what did not.
Vitaliy Kharytonskiy
(Solution Architect, Prom.ua),During the lecture, Mykyta will share the story of Solidgate's journey in building a high-performing and reliable fintech company, striving for 99.999% uptime on AWS’s SaaS platform. He'll uncover numerous caveats in doing things right without full system access, addressing product requirements, and staying up to date.
Mykyta Hlushak
(Head of Infrastructure, Solidgate),Imagine you are designing a B2B service that will serve millions of businesses. This service will have dozens of different microservices with their own data, which can contain millions of records. How do you design such a database? Why is sharding not always the answer? What other options are there for such an architectural solution? I'll tell you how we at Uspacy came to serve thousands of small databases instead of a few large ones, what we've encountered and what we plan to face)
Kyrylo Melnychuk
(Uspacy, CTO),