I&#x27;ve been thinking about event sourcing while also trying to whittle down the number of languages in play in my stack.<p>It occurred to me that if you&#x27;re doing event sourcing, you could just persist actual source code that replays the log, i.e. just dump something like this to the filesystem and keep appending to it:<p><pre><code>    createUser(&quot;rbg@scotus.gov&quot;, &quot;dj85jig&quot;)
    createUser(&quot;knope@nps.gov&quot;, &quot;b85kee6&quot;)
    befriend(&quot;dj85jig&quot;, &quot;b85kee6&quot;)
</code></pre>
It seems like people usually persist to a traditional database, which gets you acces to that whole ecosystem of tools. But source files seem like a natural fit for event sourcing and I&#x27;m curious if there are examples of this approach in use? Cautionary tales?
Ask HN: Any event sourcing systems that use source files for persistence?