Designing Data-Intensive Applications Chapter 1 Notes/Overview… Like for real, they are active recall notes for me.

Message me what you see.
  • Reliability — fault vs failure tolerance, different factors that can lead to bugs and errors, how to prevents those errors, faults, and failures.
  • Scalability — The ability of a system to grow in a way that makes sense in relation to its uniqueness.
  • Maintainability — How easily a system can be maintained relation to ease of use to upkeep
  • Stores Data — This is your conventional database, e.g. SQL, MongoDB, Aurora, Dynamo
  • Remembers result of expensive operations — Cache, e.g. Redis
  • Searches Indexes — Key Value Stores — Elastisearch from AWS
  • Streams Processes — Message Queues, e.g. Apache Kafka
  • Batch Processing —e.g. Azure Batch processing




Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

The various lengths of CSS

hello, world. [03.26.2020]

GDPR — Right to Erasure

LeetCode — At least length k places away

How I built a simple Quiz App using Flutter from scratch — Part 1

StackOverFlowError: Causes & Solutions

Get Slacked with Chat Bots

Spring Initializr

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Anthony Johnson

Anthony Johnson

More from Medium

GitHub: 2 branches on PR workflow

The Battle of Odoo: The Fastest Odoo Version in 2022

Day 7: LeetCode, Mocha, CircleCI

Why can’t I write unit tests?