design – Priyank Verma

October 5, 2019

Trying to Wrap My Head Around The Dynamo Storage System: A Deep Dive

Introduction The world of databases is very interesting. To build a loveable product, a core infrastructure piece that’s needed is the data persistence layer. I find this data persistence layer to be like a tip of the iceberg, the get and the put calls have so much going under the hood that it’s mind blowing…

Software Engineering

AWS, database, design, dynamo, dynamodb, engineering, software, system
April 28, 2019

Introduction to LSM Trees: May the logs be with you

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. Introduction What will be the simplest…

Software Engineering

casandra, coding, database, db, design, interview, lsm tree, system, the
March 7, 2019

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…

Software Engineering

architecture, Atchison, Book, design, distributed systems, engineering, lee, microservices, scale, services, soa, software, summary
January 6, 2019

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…

Software Engineering

design, distributed, distributed systems, model, safety, system, system design
December 30, 2018

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…

Software Engineering

database, db, design, partitioning, scale., sharding
September 2, 2018

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…

Software Engineering

“FAT, (or, –, 1., 10, 2., 3., 4., 5., 6., A, abstractions, acceptable, accommodate, accurately, add, adding, admiration., age-old, ago., aids, all, allows, also, am, an, analytics, and, any, appropriate, architecture, are, armies, as, at, available, away, baffling., be, because, become, belief, better, bigger, brain, browsing, built, bulky, But, by, can, cannot, cause, causes, changed, changes:, code, codebase, communication, company, compared, compiler, complex., complexity, components, conceivable, Conclusion, confidence, consider, consumed, continue, curtail, customers, customized, dashboards, decomposed, decomposition, degree, deletion, deliberately, deprecated, design, designed, designers, designing, detail, detailed, development, disagree, disciplined, discussed, does, doesn’t, Don’t, duplication., each, either, Enhanced, enough, entire, entirety, errors, essential, essentials., etc., even, every, expands, experience, exploring, explosion, extensibility, extensions, extent, faster, feature, features, fill, Finding, first, flexibility, following, for, foremost, form, found, from, functional, functionality, get, getting, goal, grows, hard, hardware, has, have, help, hierarchy, higher, holds, hope, how, huge., I, I’ll, ideas, if, ignored, important, improve, in, incompatibility, Incomprehensibility, increase, increased, individual, influenced, insanely, interfaces, Internet, into, introduction, irrelevant, is, It’s, it., justify, keep, keeping, key, kill, killed, languages, largely, laws, lean, Learned, least, lessons, Let’s, lies, like, live, machines, main, maintainability., Make, Making, me, measured., memory, methodologies, mind, minimizing, modern, modules, Monolithic, more, most, much, must, my, naive, need, needed?, needless, nerve, never, new, No, Not, now, number, of, on, one, order, original, outset., over, page, paper, part, passes, Patterns., people, pinpoint, place., Plea, PM, post, power, predominant., Preface, prerequisite, presented, pressure, pretty, primary, probably, problems, programmers, programming, proper, quantity becomes, rapidly, reacted, reason, Recently, reduce, Reducing, reflect, related, release?, remember, remove, rendered, required, requires, resonated, Resources, responses, responsibility, return, root., run, saw, seem, sell.”, sensitive, should, significant, similar, simple, simpler, single, size, slower, small, software, Solution, some, something, sophistication, sparked, specification, standard, started, state, step, Still, streamline, streamlined, Strongly, structures, suggested, sure, suspicion, system, systems., take, taking, teach, team, teams, than, than quality. Every, that, that’s, the, their, them., there, these, things, this, three, time., to, Today, toll, too., tools, topic, touch, true, two, typed, understood, unrecognized., us, usage?, use, user, versions, very, was, way, we, were, what, when, which, while, with, write, wrong., years
May 21, 2018

Tracking Metrics to Surface and Solve Problems: Metric Tracking Practices I’ve Learned So Far

It is a nice pleasant evening, you are sipping coffee and reviewing your code one final time, just so that you can gather enough confidence to hit the deploy button. But a fact of life as a software engineer is that things can go wrong. Small changes may result in unexpected outcomes, including outages, errors…

Software Engineering

(or, 1., 2., 3., 4., A, A/B, able, activity, adding, affect, all, also, an, and, any, APIs, Application, approach, are, areas, arise., as, at, automated, available, be, been, before, built, business, But, button., by, can, catch, changes:, checklist, checks, citizen, clients, code, coffee, collected, come, communication, Conclusion, confidence, configurability, continually, coverage, creating, customers, data, defines, deploy, deployment, design, designing, DevOps, directly, disciplined, do, Don’t, ease, either, Enable, engineer, engineers, enough, equipments., errors, etc., even, evening, everything., Examples, extensibility, eye, fact, feature, final, fire., first-class, folks!, following, for, from, functioning, gather, Go, handbook, have, having, health, Here, high, hit, I, I’ve, idea., impacting, impacts, importance, imported, improve, in, include, include CPU, including, industry, infrastructure, into, intuitions., involve, IOPS, is, It’s, it., items, just, keep, key, latency, latent, level, levels., leverage, life, limited, may, me, measure., measured., memory, method, metrics, multiple, must, need, needed?, negatively, nice, Not, number, numbers, occur, of, on, one, ones, only, organization., our, outages, outcomes., over, parts, pipeline, places., pleasant, points, problem, problem-solving, problems, process, processed, product, product-related, Progress, queries, quickly., random, rather, realize, really, receiving, relies, rely, remote, resolve, response, result, results, reviewing, right, runs, sales, see, sent, sipping, small, So, software, solve, spent, spikes, successful, surface, systems., task, Telemetry, test, than, that, that’s, the, these, they, things, Thus, time., to, toggling, too., total, track, tracked, tracking, transactions, unexpected, usage?, useful, validations, we, well, what, when, which, will, with, write, wrong., you, Your
May 5, 2018

Organization Archetypes And The Concept Of Market-Oriented “Solver Teams”

Organizations which designs systems are constrained to produce designs which are copies of the communication structure of the organization. In other words, how we organize our teams has a powerful effect on the software we produce, as well as our resulting architectural and production outcomes. Thus, in order to get a fast flow of work from…

Uncategorized

“E-Shaped”, “Solver, A, a bunch of, a fast, able, admins, advantage., Advantages, all, also, an, analysis, and, Another, Archetypes, architectural, architecture, are, areas, as, at, attempt, be, because, becoming, being, benefits, bring, Broadly, business, But, call, called, can, capabilities, centralize, combine, communication, complicated, composed, comprehensive, conception, Conclusion, constrained, contribute, copies, cost., coupled, covering, cross-disciplinary, cross-functional, customer, data, deliver, delivery, dependencies, deployment, design, designs, develop, development, DevOps, disciplines, division, done, dramatically, each, effect, Enable, Enables, enabling, engineering, engineers, entire, etc., ever, every, Ex., execution, experiments, expertise, experts, fast, faster, feature, flat, flow, folks!, for, from, functional, Functional-oriented:, generalist, get, great, has, have, having, helps, hierarchical, high, highly, how, idea., impact, improves, in, increasing, independently, inform, innate, instead, interesting, is, it., knowledge, launch, learning, like, machine, major, managers, market, market-oriented, marketing, Matrix-oriented:, matrix and market., member, members, move, much, multi-specialist, multiple, must, nature, needs., Not, number, of, on, only, operational, Operations, opportunities, optimizations, optimize, order, organization., Organizational, Organizations, organize, orientation., other, our, outcomes., overwhelming., own, person, plays, point, points, poorly, powerful, prevent, primarily, problem, problems, produce, production, provides, quality, quickly., Reducing, rely, reporting, respond, responding, responsible, resulting, results, retirement, safely, same, saw, Server, service, services, single, small, smoother, software, solve, solving, speaking, specialist, specialists., speed, Squad, SREs, start, stream, stream: functional, structure, structured, structures, successful, support., systems., tall, team, teams, technologies., tend, testing., than, that, that’s, the, their, them., there, these, they, they’ll, this, three, Thus, tightly, to, tracking, types, user, value, waiting, want, we, well, when, which, who, with, without, words, work, working
March 25, 2018

Practical Problem Solving Framework: Inspired By The Toyota Way

We all will agree to a certain point that having a system/process for anything reduces chances of errors. As an engineer or someone people look forward to propose solutions to problems it’s beneficial to have a framework in place to solve problems effectively. Recently I was reading The Toyota Way, and it suggested a framework to Practical Problem…

Uncategorized

books, business, coding, design, developer, engineer, entrepreneurship, framework, fun, ideas, inspiration, Internet, lean, learning, problem, programming, software, solving, technology, toyota
March 11, 2018

8 System Design Principles I learned After Doing It Wrong More than 50 Times!

At Squad, we strive to build awesome products to solve customer(internal and external) needs. As a product engineer, paramount part of your job is to design and build products. Dig deep into the root cause of the problems, design solutions and implement them as the end product. Over the course of my journey so…

Uncategorized

8, coding, deisgn pattern, design, engineer, engineering, google, how, iterate, lean, pattern, principles, product, programming, ship, software, software engineing, system, technology

Tag: design