<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>rust on Zainpay Engineering</title>
    <link>https://blog.zainpay.ng/tags/rust/</link>
    <description>Recent content in rust on Zainpay Engineering</description>
    <generator>Hugo</generator>
    <language>en-NG</language>
    <lastBuildDate>Sat, 08 Aug 2026 09:00:00 +0100</lastBuildDate>
    <atom:link href="https://blog.zainpay.ng/tags/rust/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>What We Learned When We Rewrote Zainpay&#39;s Backend in Rust</title>
      <link>https://blog.zainpay.ng/posts/what-we-learned-rewriting-zainpays-backend-in-rust/</link>
      <pubDate>Sat, 08 Aug 2026 09:00:00 +0100</pubDate>
      <guid>https://blog.zainpay.ng/posts/what-we-learned-rewriting-zainpays-backend-in-rust/</guid>
      <description>&lt;p&gt;In early 2021, Zainpay&amp;rsquo;s entire backend ran on a technology stack most business owners have never heard of: Scala and something called Akka. To our engineering team, it was elegant. The &amp;ldquo;actor model&amp;rdquo; — a way of handling thousands of simultaneous payment requests without them crashing into each other — felt like the right foundation for a payments company.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
