container-startup-autoscaler (CSA) is a Kubernetes controller that modifies the CPU and/or memory resources of containers depending on whether they're starting up, according to the startup/post-startup settings you supply. CSA works at the pod level and is agnostic to how the pod is managed; it works with deployments, statefulsets, daemonsets and other workload management APIs.

Processes kubectl outputs to enable vim-like navigation in a buffer for your cluster.

Falco is a cloud native runtime security tool for Linux operating systems. It is designed to detect and alert on abnormal behavior and potential security threats in real-time.

DiceDB is an open-source, fast, reactive, in-memory database optimized for modern hardware. Commonly used as a cache, it offers a familiar interface while enabling real-time data updates through query subnoscriptions. It delivers higher throughput and lower median latencies, making it ideal for modern workloads.

STU is the TUI explorer application for Amazon S3 (AWS S3) written in Rust using ratatui.

xan is a command line tool that can be used to process CSV files directly from the shell.

OpenProject is the leading open source project management software.

We all can agree that the most important purpose of a post-incident review (or post-mortem) is to learn from incidents. Implied in this learning is improving the system (people, processes, technology, and their interactions). All my reflections on the “5 Whys” technique refer back to how the technique enhances our learning (or not) from incidents.

Some thinking, trade-offs, theory building, and method-making one might ended up doing, in the course of bringing Infrastructure as Code (IaC) discipline to brownfield (and greenfield) services, at a small regulated fintech company, having a smaller engineering team that serves several business units, including one of India's largest national tax gateways. Only somewhat easier than reading a long compound sentence without pausing for breath. Phew.

In this article, we'll break down the infrastructure required to achieve a target of 10 million requests in 10 minutes, all for around $0.0116. This guide goes beyond basic setup and explores practical considerations for production-ready systems, balancing cost efficiency and high availability.

Thirteen years of running in EC2.

Thirteen years of custom AMIs. Thirteen years of deployment pipelines put together with toothpicks and bubblegum. Thirteen years of launch noscripts that really-do-seem-to-be-an-anti-pattern-but-hey-at-least-they-work.

And we threw it all away to run in EKS.

This is the choice we made at GumGum in early 2023, and this blog post covers the problems that led to this insane idea, and why this idea wasn’t so insane after all.

Solving IP exhaustion in EKS: Avoiding a network outage by implementing custom networking