#eventsourcing

Live, measured metrics for the hashtag #eventsourcing from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.

hashtag.org network · sponsored

Own #eventsourcing

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.

$5.00/ year · 13-character #name
Claim #eventsourcing — $5.00/yr→Buy on hashtag.space (web3)
card via hashtag.org · tokens via hashtag.space
4
Uses / 7 days
Mastodon
3
Accounts / 7 days
Mastodon
40
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 40
0
Avg reactions / post
Mastodon · last 40
—
Reddit posts / month
Reddit search
—
Open-web mentions
hashtag.org Firehose

Day-by-day usage

measured · mas.to (Mastodon public tags API) · fetched 2026-10-24 15:33 UTC
1
10-18
0
10-19
1
10-20
0
10-21
0
10-22
2
10-23
0
10-24

4 uses by 3 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.

Related hashtags

measured · mas.to (Mastodon public search API) · fetched 2026-10-24 15:33 UTC
#eventsourcinglive
0 uses · 0 accounts / 7d
#eventsourcingallow
0 uses · 0 accounts / 7d

Live pulse

measured · mas.to (Mastodon tag timeline) · fetched 2026-10-24 15:33 UTC

Everything below is measured over the latest 40 public posts (spanning ~2590 hours).

Posting hours (UTC) — busiest: 08:00

00:0012:0023:00

Languages: English (25) · German (15)

Avg boosts / post: 1.4

Top of the latest posts

  • We released 1.5.0 of laravel-event-sourcing! See here for the changelog: https://github.com/patchlevel/laravel-event-sourcing/releases/tag/1.5.0 #PHP #DDD #EventSourcing #Laravel

    patchlevel@[email protected]♥ 1↻ 22026-10-07 17:51 UTCView post →

  • I've been building skilj: a Rust library for event-sourced apps on plain Postgres. No fixed aggregates. It uses Dynamic Consistency Boundaries: a command is checked against exactly the tagged events it needs. "Enroll student in course" chec

    Gerard Klijs :rust:@[email protected]♥ 0↻ 02026-10-23 08:03 UTCView post →

  • skilj 0.1.1 is out 🦀 Event sourcing in Rust on one Postgres database, without aggregates: tag your events, and each command is checked against exactly the events it shares tags with. Try it without setting up a database: cargo generate --g

    Gerard Klijs :rust:@[email protected]♥ 0↻ 02026-10-23 08:02 UTCView post →

#eventsourcing across platforms

every network with a public tag surface

Follow #eventsourcing 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.

X (Twitter) ↗Instagram ↗TikTok ↗Facebook ↗LinkedIn ↗YouTube ↗Threads ↗Bluesky ↗Mastodon ↗Reddit ↗Pinterest ↗Tumblr ↗

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/eventsourcing