Featured

A plea for lean software: 6 Lessons I learned to help keep software simple

  Preface Recently, I was browsing the codebase of my company and saw that it has three versions of dashboards for an analytics page in it. I am pretty sure that customers don't need that. This sparked something in my naive brain and I started exploring the internet for related ideas. That's when I found … Continue reading A plea for lean software: 6 Lessons I learned to help keep software simple

Advertisements

Architecting for Scale by Lee Atchison: Reading Experience

I recently read the book Architecting for Scale by Lee Atchison. The book contains a high-level overview of the major concepts that revolve around the topic of building highly-available and scalable apps.I felt the book to be more suited as a light read for people already familiar with these concepts rather than being an informative … Continue reading Architecting for Scale by Lee Atchison: Reading Experience

How To Objectively Reason About Systems: Correctness Properties Of A System

This post is a part of a newsletter that I run: "Scamming The Coding Interview", which is geared towards helping people ACE their coding interviews. We send a coding question on weekdays along with a system design article like this one on weekends. Do subscribe If you find this article valuable. When a new system … Continue reading How To Objectively Reason About Systems: Correctness Properties Of A System

Basics of Database Partitioning and Partition Strategies

You are a part of a startup which has recently scaled to reach a huge number of users. This means that the increased number of users are going to generate a huge amount of data that you have to store and manage.It soon becomes evident that managing a huge dataset is a major hurdle to … Continue reading Basics of Database Partitioning and Partition Strategies

Why systems fail and what can be done about it?

A recent team meeting at Squad touched the topic of "system robustness". Clients and business operations want their systems to work, which is a very reasonable expectation. That's what we engineers are paid for after all. Everybody gave their input over what a robust system means to them. The responses made two points very clear:1. … Continue reading Why systems fail and what can be done about it?

Tackling Lost Updates Problem In Database Using Stricter Transaction Isolation Level

Introduction Databases are made for scale and are a highly concurrent system. Thus it is normal for them to expect multiple concurrent connections. Also, in most situations, we'll want our database to be the source of truth and always contain consistent data. There are many concurrency related phenomena that can occur in a database when … Continue reading Tackling Lost Updates Problem In Database Using Stricter Transaction Isolation Level

Practical Design Patterns Part 1: The Command Pattern

Introduction Most software these days support undoing/redoing actions. For example, text editors support undoing what we have written, file managers support undoing file creation/deletion etc. It's a good UX practice to make software forgiving and allow users to undo their actions. I always wondered how was this implemented?  On a critical analysis, it seems as … Continue reading Practical Design Patterns Part 1: The Command Pattern