<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>System-Design on Ou David | Systems Engineer</title><link>https://preview.vvivid.dev/tags/system-design/</link><description>Recent content in System-Design on Ou David | Systems Engineer</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Wed, 21 Jan 2026 08:48:01 +0100</lastBuildDate><atom:link href="https://preview.vvivid.dev/tags/system-design/index.xml" rel="self" type="application/rss+xml"/><item><title>Handling Fractional Cents in Integrations</title><link>https://preview.vvivid.dev/posts/handling_fractional_cents_integration/</link><pubDate>Wed, 21 Jan 2026 08:48:01 +0100</pubDate><guid>https://preview.vvivid.dev/posts/handling_fractional_cents_integration/</guid><description>&lt;p&gt;I&amp;rsquo;m back with another story about a &amp;ldquo;silent error&amp;rdquo; in our systems. In my &lt;a href="https://preview.vvivid.dev/posts/the_silent_timezone_mismatch_go_vs_mongodb"&gt;previous post&lt;/a&gt;, I talked about how implicit timezone conversions can bite you. Today, let&amp;rsquo;s talk about a different type of error: a design flaw when dealing with money.&lt;/p&gt;
&lt;h3 id="the-real-problem"&gt;The Real Problem&lt;/h3&gt;
&lt;p&gt;We are building a Central Reservation System (CRS) for a tourist park. One of our golden rules when dealing with money is simple: &lt;strong&gt;always use integers&lt;/strong&gt;. We convert everything to cents before pushing it to our cash-register API.&lt;/p&gt;</description></item></channel></rss>