Designed an Event Store library as one piece to do event sourcing in Clojure: https://github.com/simplemono/eventstore Here a small example to see it in action: https://github.com/maxweber/todo-sqlite-eventstore Why I want to use it for our projects 😄 We are running a SaaS with a cell-based architecture. More tenants on a cell (a dedicated server) means less disk space left. Events are immutable, so disk usage will always increase. Events will only be deleted, when the tenant (customer) is being deleted. The eventstore library allows you to store the events (source of truth) on a S3-compatible object-store. To avoid that your write-latency is becoming a nightmare you should better have one event-stream per tenant and use an object-store like Tigrisdata, Amazon S3 Express One Zone or Google Cloud Storage Rapid Bucket (which all offer a relatively low write latency). Queries will be done on your read-model that could for example be a Sqlite db on the local disk. The events are the essential state while the read-model(s) are derived state. For a schema migration, disaster recovery or when you move a tenant from on cell to another, you just replay the events to recreate your read-model (Sqlite db file). Therefore you do not need to setup Litestream or any other backup mechanism for the read-model (you still can store snapshots if you want to reduce the time-to-recovery). Next up is to extract a event-projection library from one of our branches. Let me know if you find any design flaws in the eventstore library. Thanks.
New flowstorm https://www.flow-storm.org/ and https://github.com/flow-storm/clojurescript/ releases! FlowStorm 4.6.0 : New features : • Add support for correctly recording ClojureScript async/await executions • Add https://flow-storm.github.io/flow-storm-debugger/user_guide.html#_power_stepping (specially useful for stepping async/await functions) • https://flow-storm.github.io/flow-storm-debugger/user_guide.html#_goto_to_fileline now searches files with ends-withs? for improved UX Bug fixes : • Fix multi thread timeline viewer running out of colors • Fix flow-storm.runtime.indexes/detailed-total-order-timeline ClojureScriptStorm 1.12.145-1 : • Rebaeses on top of 1.12.145 (async/await support) • (Breaking change) Tracing callbacks are now called with an extra param (frame-id) For any questions or feedback please show up in #C03KZ3XT0CF on create an issue!