/Kislay Verma

The Mechanics Of Software Evolution tl;dr: "Use feature requests as a breeding ground for the next generation of the system’s architecture. By continuously evaluating what we are being asked to change, we can jump the gun and get to the next level faster and often more safely."

featured in #312

On Building Scalable Systems tl;dr: "Scalability is the idea that a system should be able to handle an increase in workload by employing more computing resources without significant changes to its design." The key axes of scalability are latency, throughput & capacity. Kislay discusses each, as well as how to quantify scalability, and more.

featured in #303

Architecture Patterns: Caching tl;dr: "Depending on the type of application, the type of data, and the expectation of failure, there are several strategies that can be applied for caching." Kislay discusses the levels in a systems architecture where caching commonly occurs and various caching strategies, such as read through, write through, write behind. 

featured in #302

Building Robust Distributed Systems tl;dr: "I have written before on this blog about what distributed systems are and how they can give us tremendous scalability at the cost of having to deal with a more complicated system design. Let’s discuss how we can make a distributed system resilient to random failures which get more common as the system gets larger."

featured in #299

Independence, Autonomy, And Too Many Small Teams tl;dr: The concepts behind two pizza teams - mission and independence - have been lost. Teams no longer work on customer problems but a subset of those problems. This requires a lot more cross team collaboration, creating bottlenecks and inefficiencies.

featured in #196