Add RU an EN Zevaykin PB (#8086)

Pseudolukian · blinkov · web-flow · commit 89028b7637bb · 2024-09-17T08:50:48.000+03:00
Co-authored-by: Ivan Blinkov &lt;ivan@ydb.tech&gt;
diff --git a/ydb/docs/en/core/public-materials/_includes/conferences/2024/Qcon.md b/ydb/docs/en/core/public-materials/_includes/conferences/2024/Qcon.md
@@ -0,0 +1,23 @@
+## {{ ydb-short-name }}: dealing with Big Data and moving towards AI {#2024-qcon}
+
+{% include notitle [general_tag](../../tags.md#general) %}
+
+{{ ydb-short-name }} is a versatile, open-source Distributed SQL database management system that combines high availability and scalability with strong consistency and ACID transactions. It provides services for machine learning products and goes beyond traditional vector search capabilities.
+
+{% include [no_video](../../no_video.md) %}
+
+**Outline**:
+
+This database is used for industrial operations within Yandex. Among its clients are Yandex Market, Yandex Alice, and Yandex Taxi, which are some of the largest and most demanding AI-based applications.
+
+The database offers true elastic scalability, capable of scaling up or down by several orders of magnitude.
+
+Simultaneously, the database is fault-tolerant. It is designed to operate across three availability zones, ensuring continuous operation even if one of the zones becomes unavailable. The database automatically recovers from disk failures, server failures, or data center failures, with minimal latency disruptions to applications.
+
+Currently, work is underway to implement accurate and approximate nearest neighbor searches for machine learning purposes.
+
+**Takeaways**:
+* Architecture of a distributed, fault-tolerant database.
+* Approaches to implementing vector search on large datasets.
+
+[Slides](https://presentations.ydb.tech/2024/en/qcon/ydb_vector_search/presentation.pdf)
diff --git a/ydb/docs/en/core/public-materials/_includes/conferences/2024/coscup.md b/ydb/docs/en/core/public-materials/_includes/conferences/2024/coscup.md
@@ -4,6 +4,8 @@
 
 PostgreSQL is an implementation of SQL standard with one of the most vibrant ecosystems around it. To leverage all the tools and libraries that already know how to work with PostgreSQL, emerging database management systems that bring something new to the market need to learn how to mimic PostgreSQL. In this talk at [COSCUP 2024](https://coscup.org/2024/en/session/XZ98GN) [{{ team.blinkov.name }}]({{ team.blinkov.profile }}) ({{ team.blinkov.position }}) explores possible approaches to this and related trade-offs, as well as reasoning why YDB chose a unique approach to bring serializable consistency and seamless scalability to the PostgreSQL ecosystem.
 
+{% include [no_video](../../no_video.md) %}
+
 The presentation is suitable for people interested in trade-offs during implementation of PostgreSQL-compatible DBMS.
 
 [Slides](https://presentations.ydb.tech/2024/en/coscup/presentation.pdf)
diff --git a/ydb/docs/en/core/public-materials/_includes/conferences/2024/kubecon-hongkong.md b/ydb/docs/en/core/public-materials/_includes/conferences/2024/kubecon-hongkong.md
@@ -4,6 +4,8 @@
 
 YDB is an open-source distributed database management system that, for performance reasons, uses raw disk drives (block devices) to store all data without any filesystem. It was relatively straightforward to manage such a setup in the bare-metal world of the past, but the dynamic nature of cloud-native environments introduced new challenges to keep this performance benefit. In this talk at [KubeCon + CloudNativeCon + Open Source Summit Hong Kong](https://kccncossaidevchn2024.sched.com/event/1eYZz), [{{ team.blinkov.name }}]({{ team.blinkov.profile }}) ({{ team.blinkov.position }}) explores how to leverage Kubernetes and the Operator design pattern to modernize how stateful distributed database clusters are managed without changing the primary approach to how the data is physically stored.
 
+@[YouTube](https://youtu.be/hXi7k2kGc38?si=K0yQ-CVJklXJe7Hq)
+
 YDB是一个开源的分布式数据库管理系统，为了性能考虑，使用原始磁盘驱动器（块设备）存储所有数据，而不使用任何文件系统。在过去的裸金属世界中管理这样的设置相对比较简单，但云原生环境的动态特性引入了新的挑战，以保持这种性能优势。在这次演讲中，我们将探讨如何利用Kubernetes和运算符设计模式来现代化管理有状态的分布式数据库集群，而不改变数据物理存储的主要方法。
 
 [Slides](https://presentations.ydb.tech/2024/en/kubecon_hongkong/presentation.pdf)
diff --git a/ydb/docs/en/core/public-materials/_includes/conferences/2024/stackconf.md b/ydb/docs/en/core/public-materials/_includes/conferences/2024/stackconf.md
@@ -0,0 +1,17 @@
+## An approach to unite tables and persistent queues in one system {#2024-stackconf}
+
+<div class = "multi-tags-container">
+
+{% include notitle [general_tag](../../tags.md#general) %}
+
+{% include notitle [database_internals](../../tags.md#database_internals) %}
+
+</div>
+
+People need databases to store their data and persistent queues to transfer their data from one system to another. We’ve united tables and persisted queues within one data platform. Now you have a possibility to take your data from a queue, then process it and keep the result in a database within a single transaction. So your application developers don’t need to think about data inconsistency in cases of connection failures or other errors.
+
+@[YouTube](https://youtu.be/LOpP47pNFGM?si=vAXyubijAA31QaTR)
+
+[{{ team.kalinina.name }}]({{ team.kalinina.profile }}) ({{ team.kalinina.position }}) tell you about an open-source platform called YDB which allows you to work with tables and queues within a single transaction. Elena walk you through architecture decisions, possible scenarios, and performance aspects of this approach.
+
+[Slides](https://presentations.ydb.tech/2024/en/stackconf/tables-and-persistent/presentation.pdf)
diff --git a/ydb/docs/en/core/public-materials/_includes/no_video.md b/ydb/docs/en/core/public-materials/_includes/no_video.md
@@ -0,0 +1,5 @@
+{% note info %}
+
+The video will be available later.
+
+{% endnote %}
diff --git a/ydb/docs/en/core/public-materials/videos.md b/ydb/docs/en/core/public-materials/videos.md
@@ -13,6 +13,10 @@ Video recordings from conferences and webinars. The materials are divided by cat
 
   {% include [COSCUP](./_includes/conferences/2024/coscup.md) %}
 
+  {% include [Qcon](./_includes/conferences/2024/Qcon.md) %}
+
+  {% include [stackconf](./_includes/conferences/2024/stackconf.md) %}
+
   {% include [TechInternals](./_includes/conferences/2024/TechInternals.md) %}
 
   {% include [Conf42](./_includes/conferences/2024/Conf42.md) %}
diff --git a/ydb/docs/en/presets.yaml b/ydb/docs/en/presets.yaml
@@ -24,3 +24,8 @@ default:
         name: Alexander Smirnov
         position: Technology Expert at Nebius
         profile: https://www.linkedin.com/in/alexander-smirnov-bb990434/
+      kalinina:
+        name: Elena Kalinina
+        position: Technical Project Manager
+        profile: https://www.linkedin.com/in/elena-kalinina-2907b398/
+
diff --git a/ydb/docs/ru/core/public-materials/_includes/conferences/2023/HighLoad_part_2.md b/ydb/docs/ru/core/public-materials/_includes/conferences/2023/HighLoad_part_2.md
@@ -8,7 +8,7 @@
 
 </div>
 
-5 лет назад Яндекс перешел с Kafka на собственную разработку поверх YDB. С тех пор Yandex Topic Service сильно подрос по нагрузке и вышел в Open Source. В этом докладе {{ team.zivaykin.name }} ({{ team.zivaykin.position }}) рассказывает про ускорение YDB Topic Service и приводит сравнение с конкурентами.
+5 лет назад Яндекс перешел с Kafka на собственную разработку поверх YDB. С тех пор Yandex Topic Service сильно подрос по нагрузке и вышел в Open Source. В этом докладе {{ team.zevaykin.name }} ({{ team.zevaykin.position }}) рассказывает про ускорение YDB Topic Service и приводит сравнение с конкурентами.
 
 @[YouTube](https://www.youtube.com/watch?v=I-6SS6_C1Cw&list=PLH-XmS0lSi_yksBrXBOIgnuW_RmwfLKYn&index=22&pp=iAQB)
 
diff --git a/ydb/docs/ru/core/public-materials/_includes/conferences/2024/IT_picnic.md b/ydb/docs/ru/core/public-materials/_includes/conferences/2024/IT_picnic.md
@@ -0,0 +1,11 @@
+### Гарантии доставки сообщений в {{ ydb-short-name }} Topics {#2024-it-picnic}
+
+{% include notitle [database_internals_tag](../../tags.md#database_internals) %}
+
+[{{ team.zevaykin.name }}]({{ team.zevaykin.profile }})({{ team.zevaykin.position }}) продемонстрировал базовые проблемы ненадежной передачи данных и способы борьбы с ними: повторы и дедупликацию. На примере паттернов микропроцессорной архитектуры он проиллюстрировал гарантии доставки: at-most-once, at-least-once, exactly-once.
+
+@[YouTube](https://youtu.be/bdj_JrRPju0?si=392etOk5RyZVY6Kp)
+
+В завершение выступления Александр показал детали реализации гарантий доставки на примере двух брокеров очередей сообщений: Kafka и {{ ydb-short-name }} Topics.
+
+[Слайды](https://presentations.ydb.tech/2024/ru/it_picnic/ydb_topics/presentation.pdf)
diff --git a/ydb/docs/ru/core/public-materials/_includes/conferences/2024/Saint_HighLoad.md b/ydb/docs/ru/core/public-materials/_includes/conferences/2024/Saint_HighLoad.md
@@ -0,0 +1,23 @@
+### Гарантии доставки сообщений в {{ ydb-short-name }} Topics {#2024-saint-highload}
+
+{% include notitle [database_internals_tag](../../tags.md#database_internals) %}
+
+[{{ team.zevaykin.name }}]({{ team.zevaykin.profile }}) ({{ team.zevaykin.position }}) рассмотрел основные проблемы ненадёжной передачи данных и методы борьбы с ними: повторы и дедупликацию. Александр на примере паттернов микропроцессорной архитектуры продемонстрировал гарантии доставки: at-most-once, at-least-once, exactly-once.
+
+Александр с докладом «Гарантии доставки сообщений в {{ ydb-short-name }} Topics» выступал на конференциях Saint HighLoad++ 2024 и ИТ-Пикник 2024:
+
+{% list tabs %}
+
+- Saint HighLoad++ 2024
+
+    @[YouTube](https://youtu.be/6l64n8t8Ivs?si=coC70xmfuaoIzxPA)
+
+- ИТ-Пикник 2024
+
+    @[YouTube](https://youtu.be/bdj_JrRPju0?si=392etOk5RyZVY6Kp)
+
+{% endlist %}
+
+В заключение Александр на примере двух брокеров очередей сообщений — Kafka и {{ ydb-short-name }} Topics — показал детали реализации гарантий доставки.
+
+[Слайды](https://presentations.ydb.tech/2024/ru/saint_highload/ydb_topics/presentation.pdf)
diff --git a/ydb/docs/ru/core/public-materials/_includes/conferences/2024/Yandex_Infrastructure.md b/ydb/docs/ru/core/public-materials/_includes/conferences/2024/Yandex_Infrastructure.md
@@ -0,0 +1,11 @@
+### {{ ydb-short-name }} Topics: история взаимоотношений с Kafka {#2024-ya-inf}
+
+{% include notitle [database_internals_tag](../../tags.md#database_internals) %}
+
+Шина данных уровня Яндекса требует нестандартных решений. [{{ team.zevaykin.name }}]({{ team.zevaykin.profile }}) ({{ team.zevaykin.position }}) рассказал о том, как появился сервис {{ ydb-short-name }} Topics и какие оптимизации были в нём применены. Также Александр описал архитектуру {{ ydb-short-name }} Topics и объяснил, почему было принято решение отказаться от Kafka.
+
+@[YouTube](https://youtu.be/lZ5SUzdQO7k?si=cWx3sE6eDE_sx7f8)
+
+В завершение вы узнаете, как команда {{ ydb-short-name }} реализовала Kafka API в режиме serverless.
+
+[Слайды](https://presentations.ydb.tech/2024/ru/infra_conf/ydb_topics/presentaion.pdf)
diff --git a/ydb/docs/ru/core/public-materials/videos.md b/ydb/docs/ru/core/public-materials/videos.md
@@ -10,6 +10,10 @@
 
 - 2024
 
+  {% include [Saint_HighLoad](./_includes/conferences/2024/Saint_HighLoad.md) %}
+
+  {% include [Ya_Tech](./_includes/conferences/2024/Yandex_Infrastructure.md) %}
+
   {% include [True_Tech](./_includes/conferences/2024/True_Tech.md) %}
 
 - 2023
diff --git a/ydb/docs/ru/presets.yaml b/ydb/docs/ru/presets.yaml
@@ -108,14 +108,14 @@ default:
       name: Егор Тарасов
       position: DevOps инженер
       profile: https://www.linkedin.com/in/jorres-tarasov/
-    zivaykin:
+    zevaykin:
       name: Александр Зевайкин
       position: Технический лидер
-      profile:   
+      profile: https://www.linkedin.com/in/alexander-zevaykin-6bb8162bb/   
     zverev:
       name: Евгений Зверев
       position: Разработчик
-      profile:     
+      profile:  
     zinal:
       name: Максим Зиналь
       profile: https://www.linkedin.com/in/maxzinal
