On.System Architecture

System Architecture (and it’s subfield Software Architecture) is a discipline which is surprisingly poorly covered. In a sense, it is still more an art than a science, and usually requires somebody intimately familiar with practical systems, to tell what’s to do and what’s to avoid when building a system.

IT Hares have lots of experience in both Software Architecture and more general System Architecture, and are trying to share their knowledge (and more importantly, their feelings) about them.

The Importance of Back-of-Envelope Estimates

August 8, 2017 by • “No Bugs” Bunny

Quote:

trying to optimize out a 3e-7 performance hit is very rarely worth the trouble.

Another Quote:

With 4S/4U boxes having typical MTBFs of 3–5 years, the next question we should ask ourselves, is “Hey, will we really be able to write software which crashes much more rarely than that?”

Filed under: On.System Architecture Requirement analysis Design decisions

Tagged With: Latency Cache crazy stuff UDP Overload

Scaling Stateful Objects

June 27, 2017 by • “No Bugs” Bunny

Quote:

it is DB which is usually The Bottleneck™ – it means that we’re saving this enormous amount of load, exactly where it really matters.

Another Quote:

as discussed above, the real-world task is always about scaling the whole system, including database; and in this regard Stateless-App-based systems exhibit significant problems.

Filed under: Book: D&D of MOGs 1st beta of Vol. VII-IX On.System Architecture Distributed systems

Tagged With: Database Cache Server Scalability