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.
Allocator for (Re)Actors with Optional Kinda-Safety and Relocation
August 15, 2017 by • “No Bugs” Bunny
Quote:
Safe with relocation’ mode will allow us to eliminate dreaded ‘external fragmentation’ – which tends to cause quite a bit of trouble for long-running systems
Another Quote:
For a long while, I have been a strong proponent of message-passing mechanisms over mutex-based thread sync for concurrency purposes
Filed under: On.System Architecture(Re)ActorsOn.ProgrammingOptimizations
Read moreThe 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 ArchitectureRequirement analysisDesign decisions
Read moreScaling 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: On.System ArchitectureDistributed systemsBook: D&D of MOGs1st beta of Vol. VII-IX
Read more
Six Impossible Things Before Breakfast Ltd. © 2026. All rights reserved.
