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

Assorted Rants Tagged ‘Determinism’, page 1:

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”
[]

Historical Data in Databases. Audit Tables. Event Sourcing

Quote: “99% of reporting requests and 99.9% of analytics is purely historical”
Another Quote: “Information within the audit table should be sufficient to validate/justify current state”
[]

Deterministic Components for Distributed Systems

Quote: “Then you can recover from any single server failure in a perfectly transparent manner”
Another Quote: “after the program fails in production, we can get the input log and run it in the comfort of a developer’s machine, under a debugger, as many times as we want, and get exactly the same variables at exactly the same points as happened in production”
[]

On Zero-Side-Effect Interactive Programming, Actors, and FSMs

Abstract: “WHY are functional programming languages not popular for interactive programming purposes?” and “WHAT we can do about it?”
Quote: “IMNSHO, deterministic Actors are the very best thing in existence for interactive programming, with lots of very practical benefits (from production post-mortem, to protection of in-memory state against server faults).”
[]

Asynchronous Processing for Finite State Machines/Actors: from plain event processing to Futures (with OO and Lambda Call Pyramids in between)

Quote: “With ‘callback pyramid’ it is not easy to express the concept of ‘wait for more than one thing to complete’ , which leads to unnecessary sequencing, adding to latencies (which may or may not be a problem for your purposes, but still a thing to keep in mind).”
Another Quote: “Don’t even think of converting all of your code to a so-called Continuation-Passing-Style”
[]