#eventsourced
Live, measured metrics for the hashtag #eventsourced from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #eventsourced
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · mastodon.social (Mastodon public tags API) · fetched 2026-09-30 01:44 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-09-30 01:44 UTCNo related tags with measured usage found for #eventsourced.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-09-30 01:44 UTCEverything below is measured over the latest 21 public posts (spanning ~36093 hours).
Posting hours (UTC) — busiest: 21:00
Languages: English (19) · German (2)
Avg boosts / post: 0.5
Top of the latest posts
Turns out, I have not really declared my huge 💛 for #eventsourcing since I‘m on Mastodon. 😺 We‘re building a company-internal social card game @MaibornWolff with #golang - and it’s #eventsourced If you want to learn about the #domainlogic
It's not only #EventSourced, but Commands are stored as a write-ahead log, linking the incoming command Request to the events only if the command succeeds. If it fails, it's marked as having failed (which might be fine: it may have simply v
The (accidental?) conflation of #eventsourced and #eventdriven systems is going to be a major problem in the year ahead...
#eventsourced across platforms
every network with a public tag surfaceFollow #eventsourced straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/eventsourced