Vsevolod will share how he managed to build a profitable B2B SaaS without investments, which is used by top scientific publishers and grant agencies. What decisions were correct and helped to build everything in conditions of limited resources? What decisions were wrong? He will also talk about how to best organize teamwork in such conditions and what microservices have to do with it.

The session covers architectural strategies that keep Elasticsearch stable under heavy load: proper index and shard design, ILM policies, persistent queues in Logstash, metrics downsampling, and self-monitoring of the observability stack. Insights are drawn from operating platforms that handle terabytes of logs and millions of events per day.

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.

Since there is no single formula for rebranding, this presentation will explore best practices for aligning business strategy and communication to achieve business goals. What is the role of rebranding in business strategy? When and why is rebranding necessary? What problems does rebranding solve, and what does it not address?