<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Java on Igor Baiborodine</title>
    <link>https://dev--kiroule.netlify.app/categories/java/</link>
    <description>Recent content in Java on Igor Baiborodine</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 15 May 2026 08:00:00 -0400</lastBuildDate>
    <atom:link href="https://dev--kiroule.netlify.app/categories/java/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Legacy to Modern: Bridging Trace Flows with Dual-Writing and Alloy</title>
      <link>https://dev--kiroule.netlify.app/article/observability-dual-writing-zipkin-traces-to-tempo-with-grafana-alloy/</link>
      <pubDate>Fri, 15 May 2026 08:00:00 -0400</pubDate>
      <guid>https://dev--kiroule.netlify.app/article/observability-dual-writing-zipkin-traces-to-tempo-with-grafana-alloy/</guid>
      <description>&lt;p&gt;After &lt;a href=&#34;https://github.com/igor-baiborodine/insurance-hub/blob/main/docs/system-overview-and-migration-analysis.md#phase-1-foundational-infrastructure--environment-migration-lift-and-shift&#34;&gt;Phase 1&lt;/a&gt;,&#xA;the Insurance Hub had a stable Kubernetes runtime and a GitOps delivery loop in the QA K3s environment.&#xA;Deployments were now repeatable and the cluster could be reconciled from Git, but cross-service&#xA;troubleshooting was still constrained by the legacy tracing setup.&lt;/p&gt;</description>
    </item>
    <item>
      <title>From Push to Pull: Completing Insurance Hub Phase 1 with CI/CD and GitOps</title>
      <link>https://dev--kiroule.netlify.app/article/from-push-to-pull-completing-insurance-hub-phase-1-with-github-actions-and-flux/</link>
      <pubDate>Mon, 20 Apr 2026 08:00:00 -0400</pubDate>
      <guid>https://dev--kiroule.netlify.app/article/from-push-to-pull-completing-insurance-hub-phase-1-with-github-actions-and-flux/</guid>
      <description>&lt;p&gt;The previous &lt;a href=&#34;https://dev--kiroule.netlify.app/article/lift-completed-now-shift-making-the-insurance-hub-kubernetes-native-enough/&#34;&gt;article&lt;/a&gt;&#xA;concluded with the system successfully running on Kubernetes, yet it still relied on a manual&#xA;deployment model. While validating the cluster foundation and service manifests was a significant&#xA;milestone, it also revealed a lingering operational gap: the platform had a Kubernetes runtime, but&#xA;it lacked a Kubernetes-native delivery process.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Lift Completed, Now Shift: Making the Insurance Hub Kubernetes-Native (Enough)</title>
      <link>https://dev--kiroule.netlify.app/article/lift-completed-now-shift-making-the-insurance-hub-kubernetes-native-enough/</link>
      <pubDate>Thu, 05 Feb 2026 08:00:00 -0400</pubDate>
      <guid>https://dev--kiroule.netlify.app/article/lift-completed-now-shift-making-the-insurance-hub-kubernetes-native-enough/</guid>
      <description>&lt;p&gt;The Insurance Hub migration continues.&#xA;Following &lt;a href=&#34;https://dev--kiroule.netlify.app/article/from-docker-compose-to-kubernetes-lifting-the-insurance-hub-into-the-cloud/&#34;&gt;Phase 1&amp;rsquo;s &amp;ldquo;lift&amp;rdquo;&lt;/a&gt;&#xA;—provisioning clusters and infrastructure—we are now focusing on the &amp;ldquo;shift&amp;rdquo; required to make the&#xA;legacy system run on this new foundation. This article summarizes the targeted changes needed to&#xA;move our existing Java services into Kubernetes.&lt;/p&gt;</description>
    </item>
    <item>
      <title>From Docker Compose to Kubernetes: Lifting the Insurance Hub into the Cloud</title>
      <link>https://dev--kiroule.netlify.app/article/from-docker-compose-to-kubernetes-lifting-the-insurance-hub-into-the-cloud/</link>
      <pubDate>Tue, 11 Nov 2025 17:00:00 -0400</pubDate>
      <guid>https://dev--kiroule.netlify.app/article/from-docker-compose-to-kubernetes-lifting-the-insurance-hub-into-the-cloud/</guid>
      <description>&lt;p&gt;In the inaugural &lt;a href=&#34;https://dev--kiroule.netlify.app/article/from-java-to-go-kicking-off-the-insurance-hub-transformation/&#34;&gt;post&lt;/a&gt; of&#xA;the &lt;a href=&#34;https://dev--kiroule.netlify.app/series/insurance-hub-the-way-to-go/&#34;&gt;&amp;ldquo;Insurance Hub: The Way to Go&amp;rdquo;&lt;/a&gt; series, I unveiled my&#xA;ambitious strategy: modernizing a Java-based insurance system into a cloud-native Go application.&#xA;With that roadmap firmly in place, the past two months have been dedicated to hands-on engineering,&#xA;transitioning the vision from architectural diagrams to tangible implementation. This article chronicles&#xA;the execution of &lt;a href=&#34;https://github.com/igor-baiborodine/insurance-hub/blob/main/docs/system-overview-and-migration-analysis.md#phase-1-foundational-infrastructure--environment-migration-lift-and-shift&#34;&gt;Phase 1&lt;/a&gt;—a&#xA;foundational &amp;ldquo;lift and shift&amp;rdquo; that establishes our new cloud environment.&lt;/p&gt;</description>
    </item>
    <item>
      <title>From Java to Go: Kicking Off the Insurance Hub Transformation</title>
      <link>https://dev--kiroule.netlify.app/article/from-java-to-go-kicking-off-the-insurance-hub-transformation/</link>
      <pubDate>Mon, 28 Jul 2025 17:00:00 -0400</pubDate>
      <guid>https://dev--kiroule.netlify.app/article/from-java-to-go-kicking-off-the-insurance-hub-transformation/</guid>
      <description>&lt;p&gt;After years spent mastering Go through books, hands-on exercises, and migrating&#xA;my &lt;a href=&#34;https://github.com/igor-baiborodine/campsite-booking-go&#34;&gt;Campsite Booking API&lt;/a&gt; from Java, I’m&#xA;setting out on my most ambitious project yet: transforming a Java-based insurance system into a&#xA;modern, cloud-native Go application. This post marks the start of a comprehensive migration&#xA;journey—one that will dive into every aspect of system modernization, from architecture redesign to&#xA;deployment strategy.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Campsite Booking API : Revisited 3</title>
      <link>https://dev--kiroule.netlify.app/article/campsite-booking-api-revisited-3/</link>
      <pubDate>Fri, 17 Nov 2023 06:45:03 -0500</pubDate>
      <guid>https://dev--kiroule.netlify.app/article/campsite-booking-api-revisited-3/</guid>
      <description>&lt;p&gt;Another year passed, and I decided to return to this project again and implement a new batch of&#xA;improvements. So, continuing the&#xA;series &lt;a href=&#34;https://dev--kiroule.netlify.app/series/campsite-booking-api-java/&#34;&gt;&amp;ldquo;Campsite Booking API (Java)&amp;rdquo;&lt;/a&gt; with this installment, I&#xA;detail changes to the project and its current state.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Campsite Booking API : Revisited 2</title>
      <link>https://dev--kiroule.netlify.app/article/campsite-booking-api-revisited-2/</link>
      <pubDate>Thu, 01 Sep 2022 07:53:35 -0400</pubDate>
      <guid>https://dev--kiroule.netlify.app/article/campsite-booking-api-revisited-2/</guid>
      <description>&lt;p&gt;It has been almost a year and a half since I published the&#xA;article &lt;a href=&#34;https://dev--kiroule.netlify.app/article/campsite-booking-api-revisited/&#34;&gt;&amp;ldquo;Campsite Booking API: Revisited&amp;rdquo;&lt;/a&gt;. During this&#xA;time, I kept the project up-to-date and implemented numerous improvements. So, in this article,&#xA;which is&#xA;the second part of the series &lt;a href=&#34;https://dev--kiroule.netlify.app/series/campsite-booking-api-java/&#34;&gt;&amp;ldquo;Campsite Booking API (Java)&amp;rdquo;&lt;/a&gt;, I&#xA;describe in detail what was achieved and how.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Campsite Booking API : Revisited</title>
      <link>https://dev--kiroule.netlify.app/article/campsite-booking-api-revisited/</link>
      <pubDate>Wed, 03 Feb 2021 08:00:01 -0500</pubDate>
      <guid>https://dev--kiroule.netlify.app/article/campsite-booking-api-revisited/</guid>
      <description>&lt;p&gt;Originally the Campsite Booking API project was a coding challenge for a developer position I applied to&#xA;at &lt;a href=&#34;https://www.upgrade.com/&#34;&gt;Upgrade Inc.&lt;/a&gt;. Back then, in 2018, the coding challenge was followed by a series of&#xA;interviews, but in the end, I didn&amp;rsquo;t receive an offer. I recently revisited this project, and in this post, I go over&#xA;the various improvements and new features that have been implemented.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
