January 4, 2026

The Great Framework Wars: Why Phoenix Beats Express.js Every Time

A battle-tested developer’s controversial take on why JavaScript’s darling can’t compete with Elixir’s rising star The JavaScript community won’t like this, but it’s time someone said it: Phoenix LiveView has made Express.js obsolete for serious web applications. I’ll be honest — I used to be one of those developers who swore by Node.js. “JavaScript everywhere!”

The Great Framework Wars: Why Phoenix Beats Express.js Every Time Read More »

Building a Distributed Counter in Elixir: Leveraging the Actor Model for Fault-Tolerant Concurrency

I recently saw a blog talking about the distributed counters and what it would take to make it in java, I was like let’s see what it would take to make the same in the Elixir ❤ and Go 🙂 Distributed systems are inherently complex, but Elixir’s actor model and OTP (Open Telecom Platform) framework

Building a Distributed Counter in Elixir: Leveraging the Actor Model for Fault-Tolerant Concurrency Read More »

How the Wrong Tech Stack Killed India’s Biggest Crypto Exchange (And How Elixir Could Have Saved It)

Before the RBI ban crippled them, a series of catastrophic system failures had already sealed their fate. Here’s the technical post-mortem every fintech founder needs to read. In December 2017, Koinex was on top of the world. India’s largest cryptocurrency exchange was processing $265 million in trading volume monthly, onboarding 40,000 new users in a

How the Wrong Tech Stack Killed India’s Biggest Crypto Exchange (And How Elixir Could Have Saved It) Read More »

Building Fault-Tolerant Invoice Settlement Systems: Go vs Elixir — Part 2

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 »

Building Fault-Tolerant Invoice Settlement Systems: Go vs Elixir- Part 1

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 »

Building Fault-Tolerant Invoice Settlement Systems: The Elixir Way — OTP Makes It Simple — Part 3

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,

Building Fault-Tolerant Invoice Settlement Systems: The Elixir Way — OTP Makes It Simple — Part 3 Read More »