Hi,
We had the same in my team, and we deployed a very similar idea to work
around it !
We also have a C++ application that needs to access a lot of (sometimes
very heavy) cache files/dbs that vary a lot between environment.
The tool we are using now allows us to either record any externally rea
If you're in a place where you're hunting for major architectural patterns
to consider in what could amount to a rewrite, well, certainly there is no
free lunch. But the pattern you mention- capturing external event history-
is in the vein of Event Source systems
http://martinfowler.com/eaaDev/Eve
While not strictly Clojure-related, I thought I'd share this idea with you
here because (1) I came up with it while thinking about design from a
Clojure / functional point of view and (2) I respect your opinion. It's
very likely you'll have better ideas...
*I'm in an highly constrained situatio
