<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kotlin on Ole M.R. Rabanal</title><link>https://omrr.no/tags/kotlin/</link><description>Recent content in Kotlin on Ole M.R. Rabanal</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 01 Aug 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://omrr.no/tags/kotlin/index.xml" rel="self" type="application/rss+xml"/><item><title>Modernising a data platform for a telecom provider</title><link>https://omrr.no/projects/telecom-data-platform/</link><pubDate>Fri, 01 Aug 2025 00:00:00 +0000</pubDate><guid>https://omrr.no/projects/telecom-data-platform/</guid><description>&lt;p&gt;A legacy platform had grown across thirteen repositories, roughly sixty&#10;endpoints and around two hundred stored procedures. Nobody held the whole&#10;picture. The work was to recover the business logic buried in it, and to&#10;replace it with something that produced the same outcomes from far fewer&#10;moving parts.&lt;/p&gt;&#10;&lt;h2 id="context"&gt;Context&lt;/h2&gt;&#10;&lt;p&gt;A leading telecom provider, from August 2025, as architect through Sonat AS.&lt;/p&gt;&#10;&lt;p&gt;It is a classic pattern: an old system is given more and more responsibility&#10;over time, and grows to meet it. Business rules ended up mostly in the&#10;database, as stored procedures with no version history, no tests, and no&#10;boundary between one domain and the next. The behaviour was real and the&#10;business depended on it, but it was not written down anywhere except in the&#10;implementation.&lt;/p&gt;</description></item></channel></rss>