Part-2 of the invoice generation series in Elixir, Go vs Rust, When invoices settlement goes wrong So lets build the invoice settlement system and see if todays’ tech stack will be able to solve the 10 years old problems we faced. The Challenges We Must Solve 1. State Management 2. Error Handling 3. Concurrency 4. […]
Building Fault-Tolerant Invoice Settlement Systems: Go vs Elixir — Part 2 Read More »
This is the part-1 of the invoice settlement system. Read it here This story is the direct comparison of the system design comparison between Elixir & Go, we will build the same system in both of the languages and see which provides what benefit. Why This Story Matters Ten years ago, I was working at
Building Fault-Tolerant Invoice Settlement Systems: Go vs Elixir- Part 1 Read More »
Why Elixir Changes Everything Before we dive into code, let’s understand what makes Elixir fundamentally different. While Go makes you build reliability mechanisms manually, Elixir was born from the Erlang ecosystem — designed for telecommunications systems that needed 99.9999999% uptime (that’s 31 milliseconds of downtime per year). The Erlang/OTP philosophy is simple: “Let it crash,
Another day, another startup announcing they’re “modernizing” their stack by… choosing the same language as everyone else Walk into any tech meetup these days and you’ll hear the same conversation on repeat: “We’re migrating everything to Go!” The enthusiasm is infectious, the confidence unwavering, and the critical thinking apparently optional. It’s like watching a massive
The Great Go Rush: Why Developers Are Abandoning Better Tech for Google’s Pet Project Read More »
