𝗪𝗲 𝗠𝗼𝘃𝗲𝗱 𝗢𝘂𝗿 𝗪𝗲𝗯𝗵𝗼𝗼𝗸 𝗣𝗹𝗮𝘁𝗳𝗼𝗿𝗺 𝗙𝗿𝗼𝗺 𝗚𝗼 𝗧𝗼 𝗥𝘂𝘀𝘁

𝗪𝗲 𝗠𝗼𝘃𝗲𝗱 𝗢𝘂𝗿 𝗪𝗲𝗯𝗵𝗼𝗼𝗸 𝗣𝗹𝗮𝘁𝗳𝗼𝗿𝗺 𝗙𝗿𝗼𝗺 𝗚𝗼 𝗧𝗼 𝗥𝘂𝘀𝘁

We used Go for our webhook platform. It worked for 50K daily deliveries. Then we hit 200K deliveries. Memory usage spiked to 6GB. We found bugs in our concurrency. We spent weeks finding one race condition.

We switched to Rust for three reasons.

• No garbage collection. This stops memory pauses.
• Faster speed for JSON and HMAC tasks.
• Better types. The compiler finds errors for you.

The results show a big change.

• Idle memory: 2.8 GB to 380 MB.
• Peak memory: 6.2 GB to 1.1 GB.
• p99 latency: 340ms to 38ms.
• Speed: 2,400 to 8,200 deliveries per second.

Rust has a cost.

• The borrow checker feels hard. You fight it for weeks.
• Async Rust has a steep learning curve.
• Build times take a long time.
• Fewer libraries than Go.

You get confidence. If Rust code compiles, it works. Use Rust for I/O heavy systems. Give yourself a month to learn.

Source: https://dev.to/serwetarslan/we-rewrote-our-webhook-platform-from-go-to-rust-heres-what-happened-3kif