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:

Allocator for (Re)Actors with Optional Kinda-Safety and Relocation

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”

The Importance of Back-of-Envelope Estimates

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?””

Scaling Stateful Objects

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.”

Production Crashes. Post-factum Debugging. Logging. Replayable Deterministic Re(Actors)

Quote: “I’ve seen game companies with hundreds of thousands of dollars lost per hour of unplanned server downtime.”
Another Quote: “deterministic debugging is by far the best thing I have seen for production debugging.”

Determinism: Requirements vs Features

Abstract: Apparently, in practice there is big difference between cross-platform determinism and same-executable determinism, both in abilities they can provide, and from implementation complexity point of view
Quote: “Cross-platform determinism is the strictest definition of determinism I know; not surprisingly, there are quite a few factors which can break it”

Gradual OLTP DB Development – from Zero to 10 Billion Transactions per Year and Beyond

Quote: “to make an efficient representation usable for OLAP – we need to modify our data on its way to OLAP replicas”
Another Quote: “Each of the DB Server Apps is a replica master, but all replica targets are within the same Replica DB”