In just 20 minutes, Serhii Saraychikov, founder of A42 and one of Prozorro’s top white-hat hackers, will show why 80% of attacks begin with ordinary information gathering about your company. You’ll learn which common mistakes open the door to breaches, how automated systems find your weak spots faster than your teams, and how to build asset monitoring that actually prevents leaks. This is a must-see for CTOs who want to view their infrastructure through an attacker’s eyes and get a ready-to-use risk-control strategy without unnecessary costs.

Every engineer has their own path in IT. Mine didn’t start with polished presentations or clear plans — it started with me being lifted by a crane to fix a screen at the Metalist Stadium. Then came telecom projects, autotests, Red Hat, OpenStack, OpenShift — and a constant search for where to move next. Over time, the rough scripts I wrote just to save myself a few hours started holding production systems together. “Fires” turned into opportunities for new solutions, and experiments became experience that truly worked. And somewhere along the way, there were moments when I wanted to leave IT. But instead, DevOps01 appeared — then a community, and eventually AWS and HashiCorp ambassadorships. In this talk, I’ll share how the ongoing search for myself in the profession — and for the profession within myself — became the driving force that changed not only my career but also my life. How small initiatives grow into big systems, and how the community opens new doors.

A discussion with representatives of high-risk systems about why security architecture should be incorporated at the design and development stage, rather than added after release into production. We will talk about the risks of delayed implementation of controls, common security illusions, and practical approaches to integrating security practices into the work of product teams.

Have you ever wondered what’s really going on under the hood of distributed systems? Not those “sort of a cluster” setups with 3 nodes, I mean the real deal. The exabyte-scale beasts. In this talk, we’ll peek behind the curtains of modern infrastructure. How do systems that crunch mountains of data actually work? What patterns, principles, and engineering decisions are hiding behind truly scalable architectures? Here’s what we’ll dive into: - What the inner life of a distributed system really looks like - How a distributed app is different from a distributed system - How data storage patterns evolve into modern DBs, queues, and logs - Why “PostgreSQL in the cloud” isn’t really PostgreSQL anymore - Why Northguard might just outshine Kafka - And how new players like NewSQL are changing the game If you’re an architect, tech lead, developer or just curious about why infrastructure scales the way it does - come join! I’ll share insights you might use in your own projects (or at least see them from a new angle). P.S. Yep, there’ll be a bit of magic ✨ and a whole lot of hard truths about the distributed systems powering our world. ?

Imagine you decide to save an old, worn-out ship by replacing its engines with the most advanced ones. But instead of “sailing into a bright future,” it starts sinking even faster. This is a story about how Clean Architecture can become either a life buoy or a stone tied to a project’s neck. The first part is a chronicle of pain: the attempt to bring architectural elegance into the chaos of legacy code, where even successes felt accidental — and why “We’re just doing Clean Architecture” doesn’t always work. The second part is a story of “triumph”: when a mature team and the right approach turned Clean Architecture into the foundation of a scalable, flexible, and truly alive system. Two stories from real practice that show why the same approach can both sink a project and save it.

We wanted to make our service lightning-fast for users anywhere in the world. Edge computing looked like the perfect solution. In practice, we achieved lower latency — but also ran into a whole bunch of unexpected problems. In this talk, Igor will cover: - how they designed edge architecture for global users; - edge providers and infrastructure: what we chose and why; - which optimizations actually made a difference; - architectural trade-offs that shaped our system design; - when edge turned into an “edge-case” and forced us to find unconventional workarounds; - our failures — and the best practices we derived from them.

How to design architecture for a product that already has a successful production environment, but where you still want to launch startup-like initiatives inside it? How do you avoid breaking a stable system, keep user trust, and at the same time give the business room for experiments? - Painful cases of “heavy features” that didn’t stick - How we turned the business desire for “more and faster” into architecture - A successful case of fast features: Secret Boxes in Expirenza - Problems that came after the success of a “temporary” feature - Shifting the development team’s mindset

Nowadays, there is a wide variety of tools for documenting software architecture. However, over time the question arises: is there a tool that not only allows you to represent architectural blocks as interconnected services or components, but also includes comprehensive information about business processes, information systems, and IT infrastructure in a unified view? Such a tool is ArchiMate. ArchiMate is a modeling language for describing, visualizing, and analyzing enterprise architecture, which, together with TOGAF, becomes a powerful instrument in the hands of an architect. During his talk, Alexander will share examples of the Archimate modeling language, show how Archimate can speed up architecture documentation and analysis, and talk about how they use the modeling language at their company.

For many years, our corporate banking platform ran on a large, reliable monolith. Over time, however, technical debt, long release cycles, and module dependencies slowed us down. It was time to rethink. This is the story of an evolution for 150,000 clients: from running monolith and microservices in parallel to Domain-Driven Development with over 20 platform and product teams, from JSP to microfrontends and design systems, from IBM to Open Source. Key Takeaways: Why a stable monolith is no longer enough for modern banking Transition patterns that don’t disrupt business or harm clients Lessons from running monoliths and microservices in parallel Domain-Driven Development at scale: 20+ platform and product teams Microfrontends and design systems for faster delivery When Open Source is the right choice vs. when to buy