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.
Unchecked Exceptions for C++
June 7, 2018 by • “No Bugs” Bunny
Quote:
‘unchecked’ std::errors are treated as ‘something which should never ever happen, but in practice MAY occur as a result of potentially-recoverable bug'
Another Quote:
Failing-Fast does NOT mean we should necessarily Fail-Hard(!). In certain (production!) cases, Failing-Fast-AND-Soft IS a substantially better alternative.
Filed under: On.System ArchitectureDesign decisionsOn.ProgrammingProgramming LanguagesOn.DevelopmentDevelopment Philosophy
“Multi-Coring" and “Non-Blocking“ instead of "Multi-Threading" - with a Script
April 17, 2018 by • “No Bugs” Bunny
Filed under: On.System Architecture(Re)ActorsOtherAnnouncements
Read moreEight Ways to Handle Non-Blocking Returns in Message-Passing Programs - with Script
October 3, 2017 by • “No Bugs” Bunny
Filed under: On.System Architecture(Re)ActorsOtherAnnouncements
Read moreAllocator 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 more