The request names DistributedLock.Core, a library I could not find among the candidate sources; none of the listed products is that library, so the nearest match is a distributed-coordination tool. Celery 8 is a distributed task queue, and Testcontainers 10 provides throwaway containers for testing lock backends, though neither is a distributed lock library.
A question back: Which backend do you plan to use for DistributedLock.Core (e.g. Redis, SQL Server, ZooKeeper, etcd), and is it the .NET NuGet package you mean?
- 1
- 2
Testcontainerstestcontainers.orgverified and signed
Testcontainers runs disposable databases and services in Docker for tests 10, which can host a backend such as Redis or ZooKeeper for testing a distributed lock.
+2 community tools built for it
for agents: dotnet · testcontainers-dotnet · automation
Sources
- 8Celery - Distributed Task Queue — Celery 5.6.3 documentationdocs.celeryq.dev · read 2026-10-29
- 10Testcontainerstestcontainers.com · read 2026-10-29
For agents: the 10 actions behind this answer
ef-core · ef-core verified and signed
Get best practices for Entity Framework Core
· aio-libs Aiobotocore website read, tools not yet checked
· aio-libs Aiohttp website read, tools not yet checked
· async-std website read, tools not yet checked
A Rust library for easy and understandable async programming
router-core · router-core verified and signed
Framework-agnostic core concepts for TanStack Router: route trees, createRouter, createRoute, createRootRoute, createRootRouteWithContext, addChildren, Register type declaration, route matching, route sorting, file naming conventions. Entry point for all router skills.
c-library · ruamel.yaml.clib verified and signed
· Context7 website read, tools not yet checked
Get the latest docs into Claude, Codex, Cursor and other agents. Context7 serves current, version-specific docs and code examples for any library.
numpy · dask verified and signed
distributed · celery verified and signed
DAG · rustworkx verified and signed
Labels are the instruments' verdict and are never changed by ranking. Agents and robots get this same answer as JSON at /api/v1/find?q=…&answer=1 and through the MCP server.