IT Hare on Soft.ware
If you're in trouble and cannot find an answer to a question which goes beyond Stack Overflow...
If you have a not-so-usual solution for your problems but need to justify it to your boss...
If you like to think on your own rather than blindly follow "common wisdom" and "profound truth"...
...then 'No Bugs' Hare on Soft.ware might be the right place for you.
Your mileage may vary. Batteries not included

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.

All Not so Common Wisdoms about System Architecture, page 1:

Bringing Architecture of Operating Systems to XXI Century – Part IV. First Draft

posted by

Quote: “While L3 kernel can STILL run on MMU-less RAM-constrained MCUs, it provides responsiveness which is comparable to that of multi-stack kernels.”
Another Quote: “multi-coring is essentially a special case of balancing shared-nothing nodes”
[→]

Bringing Architecture of Operating Systems to XXI Century – Part II. Desirable Improvements

posted by

Quote: “low-end versions of the new OS should be lean enough to run on a ~$1 MCU (these days ~=4K RAM, 32K ROM)”
Another Quote: “last N minutes of the life of the production program before crashing, should be replayable on my development box.”
[→]

Bringing Architecture of Operating Systems to XXI Century – Part I. Changes in IT Over Last 50 Years

posted by

Quote: “we’re using operating systems which were designed whopping 40-50 years from now”
Another Quote: “Do not communicate by sharing memory; instead, share memory by communicating.”
[→]

Unchecked Exceptions for C++

posted by

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.”
[→]
Copyright © 2014-2016 ITHare.com