Disk

A very short Chapter 2 is about how to make rough estimates to start from the most important parts when designing the software.

Some concepts that EVERY software developer should know:

• “Power of two”
• Standard latency numbers! How fast is memory, how slow is disk, etc…
• Availability numbers
• What are key metrics you should think about

These concepts and numbers are disclosed in chapter two of the book:

“System Design Interview – An insider’s guide” by Alex Xu

The book club of our company has chosen a new wonderful book for reading:

Robert Martin - Clean Architecture - a Craftsman’s Guide to Software Structure and Design

👍

The part VI undermines some foundations 😀:

• Do you know that Database is a “detail”? An unimportant minor low-level non-essential feature that can be neglected in architecture design!
• Do you know the same about the Web? It is just an unimportant IO device that should also be neglected in architecture design!
• What about Frameworks? The same. Don’t marry your framework. Use safe and better remote sex. 🤣
• There are several examples of how similar architectures may or may not lead to problems. And what to use to avoid problems (spoiler: Encapsulation)
• All of the above, and a brief missing advice…

Great information! All the details are in my mind maps: