The driving force behind Resonate.
durable execution, distributed async await, cloud programming model, dead simple apis
Resonate is by developers, for developers.
Leave retries, crash recovery, idempotency guarantees, service discovery, load balancing, suspension, etc.. to Resonate.
Focus on your product.
Resonate APIs are the quality-of-life improvement developers have been yearning for.
The resonatehq Github org is home to Resonate's open-source component related repos. Such as:
- Resonate Server
- Resonate Python SDK
- Resonate TypeScript SDK
- Resonate TypeScript GCP FaaS Shim
- Resonate TypeScript Cloudflare FaaS Shim
- Resonate TypeScript Kafka Transport Plugin
- Resonate Docs
- Distributed Async Await Specification
- etc...
If you are looking for Resonate example applications (example apps showcasing how to use Resonate), visit the resonatehq-examples Github org.
Who is into Resonate?
The best thing to do is join the Resonate Community Discord. That is where you will find folks who are deeply interested in distributed systems engineering and who are actively using Resonate.
But you can also follow or subscribe on these platforms:
Resonate has a "zero-dependency" development experience. Apart from installing the Resonate SDk into your project, you don't need to worry about any additional components to get started.
For example, in Python:
uv add resonate-sdkOr TypeScript:
bun add @resonatehq/sdkThen initialize Resonate, and start building:
For example, in Python
from resonate import Resonate
resonate = Resonate()
@resonate.register
def foo(ctx, arg):
# ...
return resultOr TypeScript:
import { Resonate } from "@resonatehq/sdk";
import type { Context } from "@resonatehq/sdk";
const resonate = new Resonate();
resonate.register("foo", (ctx: Context, arg: string) => {
// Your function logic here
return result;
});Check out the docs for more ways to get started: Get started with Resonate
Resonate HQ makes software for other developers to use to build reliable and scalable systems.
The quality of our software is highly tied to:
- our obsession with a "simple" developer experience
- our use of specifications, protocols, formal modeling, and formal verification
- our pioneering efforts into Deterministic Simulation Testing
