#membase
Live, measured metrics for the hashtag #membase from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #membase
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.online (Mastodon public tags API) · fetched 2026-09-28 18:53 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.online (Mastodon public search API) · fetched 2026-09-28 18:53 UTCNo related tags with measured usage found for #membase.
Live pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-09-28 18:53 UTCEverything below is measured over the latest 1 public posts.
Posting hours (UTC)
Languages: English (1)
Avg boosts / post: 0
Used together with
No co-used tags in the sample.
Top of the latest posts
#Membase was a system for managing distributed key value stores. https://www.couchbase.com/blog/what-exactly-membase/ They were targeting different areas, but James Phillips (Membase co-founder) figured they'd complement each other and beco
What “membase” means
WikipediaCouchbase Server, originally known as Membase, is a source-available, distributed multi-model NoSQL document-oriented database software package optimized for interactive applications. These applications may serve many concurrent users by creating, storing, retrieving, aggregating, manipulating and presenting data. In support of these kinds of application needs, Couchbase Server is designed to provide easy-to-scale key-value, or JSON document access, with low latency and high sustainability throu
“Couchbase Server” on Wikipedia (CC BY-SA) →#membase across platforms
every network with a public tag surfaceFollow #membase 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/membase