npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@event-driven-platform/read-execution-coordinator

v0.0.3

Published

Technology-neutral distributed Read execution coordination contracts.

Readme

@event-driven-platform/read-execution-coordinator

Defines the technology-neutral distributed coordination contract for transient cross-instance Read execution ownership.

Role

After shared-cache miss, Reader may use a coordinator to ensure that only one instance owns downstream source work for a deterministic ReadCacheKey while followers wait and later re-read shared cache.

shared cache miss
-> claim
   -> owner continues
   -> followers wait
-> result rendezvous happens through shared cache

The coordinator transports ownership, not the read result.

Ownership model

A successful claim returns a ReadExecutionLeaseReference containing ownerId and monotonic ownership version. Renewal extends the current generation. Renew and release must verify the complete ownership reference so a stale owner cannot mutate a reclaimed lease.

Lease duration is explicit and bounded. Storage technology, clock representation, and expiry implementation belong to adapters.

Followers

wait is bounded and returns explicit outcomes: released, timed-out, cancelled, or unavailable. After waiting, Reader re-reads shared cache and re-contends when the value is still absent. The coordinator never broadcasts the result.

Shared-cache requirement

Cluster-wide result coalescing requires at least one shared cache level. The owner publishes a successful result through shared cache; followers obtain it by re-reading that cache after the flight changes state.

A coordinator alone cannot provide cluster-wide result rendezvous for a local-only/no-cache topology.

Failure boundary

Coordinator availability is explicit through contract outcomes. Reader owns the execution policy. The stable Reader integration fails closed when configured distributed coordination is unavailable rather than bypassing coordination and creating uncontrolled source work.

Non-responsibilities

This package does not persist results or durable execution history, execute handlers, read/write caches, implement local single-flight, or prescribe Redis.

Related documentation