<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Overview on Nikita Ryanov</title><link>https://nryanov.com/tags/overview/</link><description>Recent content in Overview on Nikita Ryanov</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 31 Dec 2025 04:30:00 +0300</lastBuildDate><atom:link href="https://nryanov.com/tags/overview/index.xml" rel="self" type="application/rss+xml"/><item><title>Different ways to setup CDC</title><link>https://nryanov.com/postgresql/cdc/</link><pubDate>Wed, 31 Dec 2025 04:30:00 +0300</pubDate><guid>https://nryanov.com/postgresql/cdc/</guid><description>&lt;p&gt;CDC is an important part of data processing. Using CDC you can achieve many goals from simple data replication to audit and complex ETL jobs.
But implementing CDC is still a tough task (especially when considering not only happy-path).
In this article I want to show different ways of implementing CDC. Also, I&amp;rsquo;ll try to not only show how to setup each variant, but also compare them with each other and highlight pros and cons of each option.&lt;/p&gt;</description></item><item><title>Delivery and processing semantics: overview</title><link>https://nryanov.com/overview/delivery-and-processing-semantics/</link><pubDate>Wed, 01 May 2024 04:30:00 +0300</pubDate><guid>https://nryanov.com/overview/delivery-and-processing-semantics/</guid><description>&lt;p&gt;In this article I want to make an overview of a delivery semantics in messaging systems, describe delivery guarantee and
add my own thoughts about all of this.&lt;/p&gt;
&lt;h1 id="delivery-semantics-overview"&gt;Delivery semantics: overview &lt;!-- raw HTML omitted --&gt;&lt;!-- raw HTML omitted --&gt;&lt;/h1&gt;
&lt;p&gt;So, what exactly is &lt;code&gt;delivery semantics&lt;/code&gt; and why this is important? &lt;code&gt;Delivery semantics&lt;/code&gt; is about guarantees provided by messaging system or delivery protocol.
These guarantees are about message order (delivery and processing), delivery reliability, duplication allowance and so on. In other words &lt;code&gt;delivery semantic&lt;/code&gt; determines how exactly message will be handled in terms of delivery.&lt;/p&gt;</description></item><item><title>Kafka-connect: overview</title><link>https://nryanov.com/kafka/kafka-connect-overview/</link><pubDate>Tue, 11 Jul 2023 04:30:00 +0300</pubDate><guid>https://nryanov.com/kafka/kafka-connect-overview/</guid><description>&lt;h1 id="kafka-connect-overview"&gt;Kafka-connect: overview &lt;!-- raw HTML omitted --&gt;&lt;!-- raw HTML omitted --&gt;&lt;/h1&gt;
&lt;p&gt;Imagine you have a task where you need to fetch some data from a database and incrementally store it in kafka or read the consumed data from kafka and store it in the database.
You can solve both tasks using plain kafka consumer/producer API or even use kafka streams library,
but if you don&amp;rsquo;t need comprehensive data transformations (e.g. enrichment, stream joining) then you can use Kafka connect for it.&lt;/p&gt;</description></item></channel></rss>