The article fails to convince me the "Memory Image Pattern" is some how different from the referenced Martin Fowler article about the pattern:Memory Image[0] from 2011, or indeed Event Sourcing[1] from much earlier (referenced by both articles). Especially when you get to the benefits an caveats this is the same concept. Events can describe the initiating action (key down), the finalizing action (key up), or some sort of aggregate (key pressed). Command and Query Result Segregation (CQRS) articles often mention being paired with the event sourcing[2] pattern to lead to the same result.
Yeah there is also: https://wiki.c2.com/?ThePrevayler (I see it footnoted in the Martin Fowler article) The idea of a transaction log to reconstruct current state of the application and to allow point in time recovery is the foundation of databases. I worked with stock exchange software that worked this way (application state was shared memory + on-disk transaction log) 20 years ago and it was by no means a novel idea at that time.
The article fails to convince me the "Memory Image Pattern" is some how different from the referenced Martin Fowler article about the pattern:Memory Image[0] from 2011, or indeed Event Sourcing[1] from much earlier (referenced by both articles). Especially when you get to the benefits an caveats this is the same concept. Events can describe the initiating action (key down), the finalizing action (key up), or some sort of aggregate (key pressed). Command and Query Result Segregation (CQRS) articles often mention being paired with the event sourcing[2] pattern to lead to the same result.
[0]: https://www.martinfowler.com/bliki/MemoryImage.html [1]: https://www.martinfowler.com/eaaDev/EventSourcing.html [2]: https://docs.microsoft.com/en-us/azure/architecture/patterns...