#cqrs
Live, measured metrics for the hashtag #cqrs from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #cqrs
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-28 14:24 UTC1 uses by 1 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-28 14:24 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 14:24 UTCEverything below is measured over the latest 40 public posts (spanning ~8164 hours).
Posting hours (UTC) — busiest: 07:00
Languages: English (19) · Russian (12) · Chinese (Taiwan) (3) · Polish (3) · French (2) · German (1)
Avg boosts / post: 0.5
Top of the latest posts
Migrating CitySim from Class Hierarchy Sim to ECS Sim Converting the #wolverine #cqrs class hierarchy simulation code where each entity is responsible for its own simulation to an #ECS based simulation using #Arch #iloggable #blog #gamedev
I broke down Event Sourcing in Quarkus using Java records, sealed types, pure functions, and a clean CQRS split. Fully hands-on. No magic. Just data, folds, and clear architecture. If you want to understand event sourcing without the hype,
CQRS, async with retries and dead-lettering, event sourcing, projections, workflows. That feature list usually means a platform team. I built it as an e-commerce shop on Tempest + Ecotone. The entire messaging layer: about a dozen small cla
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/cqrs