#evitadb
Live, measured metrics for the hashtag #evitadb from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #evitadb
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 04:04 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-28 04:04 UTCNo related tags with measured usage found for #evitadb.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 04:04 UTCEverything below is measured over the latest 13 public posts (spanning ~23440 hours).
Posting hours (UTC) — busiest: 05:00
Languages: English (13)
Avg boosts / post: 0.5
Top of the latest posts
In the last release of #evitaDB, we shipped change data capture. From now on, you can connect your application to the database's change stream via gRPC, GraphQL, or REST APIs. If you're curious about how CDC works behind the scenes, check o
The Java API of #evitaDB supports both the old synchronous approach and the new reactive approach. We've recently published an article about this feature related to transaction handling in #evitaDB. You can easily observe when your changes
Java runs on every platform. But does your application built on the JVM? You can't be completely sure unless you test it, and test it regularly. From now on, #evitaDB runs all its tests on a weekly basis for all 3 major OS architectures. So
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/evitadb