Share this page!

Enter URL or ID to Unroll

You can paste full URL like: https://x.com/threadreaderapp/status/1644127596119195649
or just the ID like: 1644127596119195649

How to get URL link on X (Twitter) App

  1. On the Twitter thread, click on or icon on the bottom
  2. Click again on or Share Via icon
  3. Click on Copy Link to Tweet
  4. Paste it above and click "Unroll Thread"!
  5. More info at Twitter Help
Dave Remy Profile picture
Dave Remy
@daveremy
CEO Event Store Ltd. Stream Database Technology, Event Sourcing, Distributed Systems, Rust lately. Mostly software/database oriented reposts.
Jul 12, 2021 • 12 tweets • 2 min read
Traditional operational databases have been ripe for disruption for years. They are lossy by design (state changes, business context) and they trap core “source of truth” data often behind aging legacy systems. Event Stores represent an alternative for operational data
1/12 I have been a CTO/CIO off and on for > 20 years & what kept me up at night was the frustration of legacy systems and the myriad hacks dealing with them. This is the elephant in the room for non-startup organizations - dealing with legacy
2/12
Jul 7, 2021 • 13 tweets • 3 min read
A cool aspect of working at Event Store is exposure to so many event sourcing projects/users/companies. A few observations (not exhaustive) …
1/13 Event Sourcing failures get a lot of attention & successes hum along quietly

Perhaps our most common support scenario is that a customer has been in production (without our knowledge, its open source) for years and suddenly has a problem they need help with
2/13
Jun 4, 2021 • 11 tweets • 2 min read
Often get asked the difference between Confluent’s Kafka & EventStoreDB. Both support durable events & have similar APIs (append to stream, subscribe to stream, ...). TLDR: Kafka was built as an integration/messaging technology, ESDB was built as a database
1/ EventStoreDB (and Event Sourcing) are about building systems in an event oriented manner. Kafka is about integrating systems that may or may themselves be event oriented
2/
Apr 6, 2021 • 19 tweets • 3 min read
Most people who learn about Event Sourcing learn it as an application design pattern, which of course it is. However, IMO, the big WHY for Event Sourcing is the Event data model that this pattern enables
1/ To date myself I was fairly early in the relational database space working for IBM in the mid 80s when relational started to take off. A big driver of relational db adoption was that Relational (vs Hierarchical) did not you require you to lock in your query access pattern
2/
Mar 30, 2021 • 33 tweets • 4 min read
A tweet stream on Event Stores as a new class of Database EventStoreDB eventstore.com is an example of an Event Store type DB.
1/ Event Stores could equally be called log, ledger, or stream databases but they came out of the Event Sourcing space which named them Event Stores. DB Engines link to Event Stores: (db-engines.com/en/ranking/eve…)
2/