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

What functions look like in various programming languages

Stamp — Technical Breakdown

How to become Employable during B-Tech

Routing external traffic into your Kubernetes services (Part 2)

CS50 Review — The BEST Course I have Ever Taken (Edx, Harvard University)

I cried after completing my nanodegree and it was worth it

Meaningful Names (Clean Code) — Why it is important for software developers?

SolFarm v1

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

What is Reactive Programming? | Interview basics

Temperature Control | Embedded Systems

Mutable, immutable…everything is an object!

Reversing a String and Checking Whether It’s a Palindrome