<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Distributed-Systems on Ole Rabanal</title><link>https://omrr.no/tags/distributed-systems/</link><description>Recent content in Distributed-Systems on Ole 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/distributed-systems/index.xml" rel="self" type="application/rss+xml"/><item><title>Modernizing 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 a dozen repositories, over sixty&#10;endpoints and more than 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 behavior 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><item><title>Invoice and debt collection subsystem</title><link>https://omrr.no/projects/debt-collection-subsystem/</link><pubDate>Sun, 01 Dec 2024 00:00:00 +0000</pubDate><guid>https://omrr.no/projects/debt-collection-subsystem/</guid><description>&lt;p&gt;A customer needed to integrate with an external debt collection service. The&#10;integration itself is not the interesting part. What a third-party vendor&#10;does to the shape of the surrounding systems, is.&lt;/p&gt;&#10;&lt;h2 id="context"&gt;Context&lt;/h2&gt;&#10;&lt;p&gt;August to December 2024, through Sonat AS, as architect and developer.&lt;/p&gt;&#10;&lt;p&gt;Rather than wiring the vendor into the applications that needed it, the&#10;integration was built as a subsystem within a distributed system, consumed by&#10;other applications through events. The supported use cases:&lt;/p&gt;</description></item><item><title>Production lines for the ParQSense sensor and base station</title><link>https://omrr.no/projects/parqsense-production-lines/</link><pubDate>Sun, 01 Dec 2019 00:00:00 +0000</pubDate><guid>https://omrr.no/projects/parqsense-production-lines/</guid><description>&lt;p&gt;Software that builds physical products has an unusual property: the output is&#10;not a result on a screen, it is a device that leaves the building and cannot be&#10;patched afterwards.&lt;/p&gt;&#10;&lt;h2 id="context"&gt;Context&lt;/h2&gt;&#10;&lt;p&gt;August 2018 to December 2019, at Q-Free ASA in Trondheim, in a supply chain&#10;team that owned both the hardware and the software for the production lines.&lt;/p&gt;&#10;&lt;p&gt;Two closely related projects, each producing one production line: one for&#10;single IoT parking sensor units, and one for the base station that multiple&#10;parking units communicate with.&lt;/p&gt;</description></item></channel></rss>