<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Pages on EXPLAIN ANALYZE</title>
        <link>https://explainanalyze.com/page/</link>
        <description>Recent content in Pages on EXPLAIN ANALYZE</description>
        <generator>Hugo -- gohugo.io</generator>
        <language>en-us</language><atom:link href="https://explainanalyze.com/page/index.xml" rel="self" type="application/rss+xml" /><item>
            <title>About</title>
            <link>https://explainanalyze.com/about/</link>
            <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
            <guid>https://explainanalyze.com/about/</guid>
            <description>&lt;p&gt;I&amp;rsquo;m &lt;strong&gt;Ruslan Tolkachev&lt;/strong&gt; — a Staff Systems Engineer with over &lt;strong&gt;15 years&lt;/strong&gt; of enterprise production experience in databases and the systems built around them.&lt;/p&gt;&#xA;&#xA;    &lt;blockquote&gt;&#xA;        &lt;p&gt;&lt;em&gt;Every database works fine at hello world. The engineering starts when it needs to scale.&lt;/em&gt;&lt;/p&gt;&#xA;&#xA;    &lt;/blockquote&gt;&#xA;&lt;p&gt;That&amp;rsquo;s where I&amp;rsquo;ve spent my career — data modeling, query performance, tuning, replication, consistency, transactions, storage engines. But a database that runs well is only half the story. The other half is everything around it — provisioning, deployment, observability, SLOs, disaster recovery, and the &lt;strong&gt;operational maturity&lt;/strong&gt; to tie it all together. &lt;strong&gt;MySQL&lt;/strong&gt; and &lt;strong&gt;PostgreSQL&lt;/strong&gt; are my core, but I also work extensively with &lt;strong&gt;Kafka&lt;/strong&gt;, &lt;strong&gt;Elasticsearch&lt;/strong&gt;, and &lt;strong&gt;Redis&lt;/strong&gt; — and wrapping it all in the operational discipline that keeps it running when it matters most.&lt;/p&gt;&#xA;&lt;p&gt;I don&amp;rsquo;t just build systems — &lt;strong&gt;I build the teams that own them&lt;/strong&gt;. Architecture decisions mean nothing without people who understand them, operate them, and make them better over time. And in the age of AI, the difference compounds — a strong engineer with the right tools doesn&amp;rsquo;t just produce more, they produce &lt;em&gt;logarithmically&lt;/em&gt; more. Building great teams has never mattered this much.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;What you&amp;rsquo;ll find on this blog:&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Scaling databases&lt;/strong&gt; beyond hello world — modeling, performance, and operational patterns&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Resilient infrastructure&lt;/strong&gt; end to end — from provisioning to disaster recovery&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;AI + engineering teams&lt;/strong&gt; — how the multiplier effect changes everything&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;15 years of enterprise production&lt;/strong&gt; — what works, what breaks, and why&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;</description>
        </item><item>
            <title>Archives</title>
            <link>https://explainanalyze.com/archives/</link>
            <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
            <guid>https://explainanalyze.com/archives/</guid>
            <description></description>
        </item><item>
            <title>Search</title>
            <link>https://explainanalyze.com/search/</link>
            <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
            <guid>https://explainanalyze.com/search/</guid>
            <description></description>
        </item></channel>
</rss>
