#eventstore
Live, measured metrics for the hashtag #eventstore from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #eventstore
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 · fosstodon.org (Mastodon public tags API) · fetched 2026-07-27 09:01 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-27 09:01 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 09:01 UTCEverything below is measured over the latest 13 public posts (spanning ~66167 hours).
Posting hours (UTC) — busiest: 18:00
Languages: English (10) · German (3)
Avg boosts / post: 2.5
Top of the latest posts
I've been working on an article for Kurrent / KurrentDB (formerly #EventStore and #EventStoreDB) and it is now published. "Implementing Domain-Driven Design with KurrentDB" https://www.kurrent.io/blog/implementing-ddd-with-kurrentdb/ #DDDes
#eventsourcing #eventstore I just published the follow-up article: "Advanced features of an Event Store for Event Sourcing" https://medium.com/@TonyBologni/advanced-features-of-an-event-store-for-event-sourcing-a457ebd77692 Mastodon first,
#EventSourcing #eventstore Here we go, new article "Essential features of an Event Store for Event Sourcing" https://medium.com/@TonyBologni/essential-features-of-an-event-store-for-event-sourcing-13e61ca4d066 There will be a second part ve
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/eventstore