<rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
  <channel>
    <title><![CDATA[ All Technology, Zero Magic ]]></title>
    <description><![CDATA[ Discoveries from area of Java and Kubernetes ]]></description>
    <link>/</link>
    <atom:link href="/rss.xml" rel="self" type="application/rss+xml"/>
    <generator>Quarkus Roq</generator>
    <lastBuildDate>Wed, 01 Apr 2026 00:00:00 +0000</lastBuildDate>
      <item>
        <title><![CDATA[Upgrading Managed Kubernetes Clusters - Azure vs AWS]]></title>
        <link>/posts/upgrading-managed-kubernetes-clusters-azure-vs-aws/</link>
        <guid isPermaLink="false">/posts/upgrading-managed-kubernetes-clusters-azure-vs-aws/</guid>
        <pubDate>Wed, 01 Apr 2026 00:00:00 +0000</pubDate>
        <description><![CDATA[I was managing a few Kubernetes clusters over the last few years and the developer experience on Azure vs AWS is... quite different. These are notes from the operations guide I had written on the topic of upgrading the clusters.]]></description>
        <content:encoded><![CDATA[<p>I was managing a few Kubernetes clusters over the last few years and the developer experience on Azure vs AWS is... quite different. These are notes from the operations guide I had written on the topic of upgrading the clusters.</p><div style="margin-top: 50px; font-style: italic;"><strong><a href="/posts/upgrading-managed-kubernetes-clusters-azure-vs-aws/">Keep reading</a>.</strong></div><br /> <br />]]></content:encoded>
      </item>
      <item>
        <title><![CDATA[Unpoly Client-Side Capabilities]]></title>
        <link>/posts/unpoly-client-side-capabilities/</link>
        <guid isPermaLink="false">/posts/unpoly-client-side-capabilities/</guid>
        <pubDate>Wed, 18 Mar 2026 00:00:00 +0000</pubDate>
        <description><![CDATA[Web applications that use Unpoly will primarily use HTML markup and custom attributes to drive interaction. It is not against the philosophy to use JavaScript — quite the opposite. Unpoly offers a very open API that lets custom code and Unpoly interact very comfortably.]]></description>
        <content:encoded><![CDATA[<p>Web applications that use Unpoly will primarily use HTML markup and custom attributes to drive interaction. It is not against the philosophy to use JavaScript — quite the opposite. Unpoly offers a very open API that lets custom code and Unpoly interact very comfortably.</p><div style="margin-top: 50px; font-style: italic;"><strong><a href="/posts/unpoly-client-side-capabilities/">Keep reading</a>.</strong></div><br /> <br />]]></content:encoded>
      </item>
      <item>
        <title><![CDATA[Unpoly Server-Side Protocol]]></title>
        <link>/posts/unpoly-server-side-protocol/</link>
        <guid isPermaLink="false">/posts/unpoly-server-side-protocol/</guid>
        <pubDate>Tue, 03 Mar 2026 00:00:00 +0000</pubDate>
        <description><![CDATA[While majority of Unpoly magic happens on the client-side the server still stays in control. Unpoly utilizes HTTP headers in request and response to steer both server and client-side actions]]></description>
        <content:encoded><![CDATA[<p>While majority of Unpoly magic happens on the client-side the server still stays in control. Unpoly utilizes HTTP headers in request and response to steer both server and client-side actions</p><div style="margin-top: 50px; font-style: italic;"><strong><a href="/posts/unpoly-server-side-protocol/">Keep reading</a>.</strong></div><br /> <br />]]></content:encoded>
      </item>
      <item>
        <title><![CDATA[Unpoly: Achieving a Single-Page Experience with Server-Side Rendering]]></title>
        <link>/posts/unpoly-achieving-a-single-page-experience-with-server-side-rendering/</link>
        <guid isPermaLink="false">/posts/unpoly-achieving-a-single-page-experience-with-server-side-rendering/</guid>
        <pubDate>Thu, 26 Feb 2026 00:00:00 +0000</pubDate>
        <description><![CDATA[I am great fan and supporter of Unpoly. It enables you to create very responsive user interfaces while enabling very reasonable server-side model and allows you to keep most of the interaction decisions at server side. I had the opportunity to speak at Devoxx Belgium about it in 2024, and this is textual version of that talk.]]></description>
        <content:encoded><![CDATA[<p>I am great fan and supporter of Unpoly. It enables you to create very responsive user interfaces while enabling very reasonable server-side model and allows you to keep most of the interaction decisions at server side. I had the opportunity to speak at Devoxx Belgium about it in 2024, and this is textual version of that talk.</p><div style="margin-top: 50px; font-style: italic;"><strong><a href="/posts/unpoly-achieving-a-single-page-experience-with-server-side-rendering/">Keep reading</a>.</strong></div><br /> <br />]]></content:encoded>
      </item>
      <item>
        <title><![CDATA[Publishing Roq to Netlify]]></title>
        <link>/posts/publishing-roq-to-netlify/</link>
        <guid isPermaLink="false">/posts/publishing-roq-to-netlify/</guid>
        <pubDate>Wed, 25 Feb 2026 00:00:00 +0000</pubDate>
        <description><![CDATA[First step in resurrecting the blog was to make it deploy to Netlify.
It ended up being quite straightforward.]]></description>
        <content:encoded><![CDATA[<p>First step in resurrecting the blog was to make it deploy to Netlify.
It ended up being quite straightforward.</p><div style="margin-top: 50px; font-style: italic;"><strong><a href="/posts/publishing-roq-to-netlify/">Keep reading</a>.</strong></div><br /> <br />]]></content:encoded>
      </item>
  </channel>
</rss>
