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.

The year is 2025. Ignoring the AI elephant in the JavaScript room is getting harder by the day. This beast, vibing along with our code, stomps all over the things we developers hold dear: clean code, architecture, our habits, and the beliefs about what's "right" and what's not. This knowledge cost me a few tens of thousands of dollars while working on a project that used AI to the max. And all I have left to show for it — is this talk. Of course, we won't be able to cover everything. But I desperately need a therapy session about the most painful part — how, through working with AI, I lost my sense of what architecture means to me... and what to do about it.

When human safety is at stake, technical reliability is not just a requirement. In this talk, we'll look at architecture, workloads, WebSocket solutions, Kubernetes scaling, and other technical aspects of creating an airborne alarm map. This is a story not only about code, but also about responsibility.

Taking a system from 66 million to over 25 billion records is not for the faint of heart—especially when the system in question is financial, where precision is non-negotiable and data latency isn’t an option. In this talk, I’ll walk through the real-world journey of scaling such a system while staying sane and keeping the numbers right. You’ll get a look at how to juggle the need for ultra-high accuracy and low-latency performance, streamline your app logic, and sidestep the usual traps that come with database scaling. This session isn’t about deep-diving into internals—it’s about sharing pragmatic strategies that help you scale without drowning in complexity. Ideal for engineers and system architects eager to tackle serious scale challenges with clarity and confidence.</p> <h4>Abstract

Today, Redis is the de facto standard for caching in application services. It’s incredibly fast and easy to use, giving it a significant advantage in the market. However, as system complexity grows, Redis has several limitations that affect the reliability and availability of your system, especially under high load. In 2025, we are gradually moving away from Redis and rethinking the caching approach as a whole. In this talk, I will share my perspective on the problem and possible solutions. We will explore the challenges associated with Redis and look at alternative solutions for building more resilient and scalable systems.

In my presentation, I will discuss the key aspects of the Zero Sales Lost strategy, focusing on incident management in the context of E-commerce development and the "Silpo" ecosystem. I will share our experience in building an incident management process, the specifics of monitoring and alerting system architecture, and how we scaled these processes across 19 products and 41 teams. Additionally, we will explore the role of DevOps culture and team responsibility in product development. Using real case studies, we will analyze whether critical failures can be prevented and how to achieve that effectively.

I'll share what problems our team faced in the process of developing and maintaining a microservice architecture software system for 5 years, what solutions we applied and how it affected us. In the talk we'll cover: domain modeling, assets topology, value of standards and soft skills

How to build cost-aware, efficient, modern architectures in practice