zuki

Why Zuki?

Most async runtimes make compromises. Zuki doesn't:

• Lock-free data structures — No mutexes, no blocking
• Zero-cost abstractions — Pay only for what you use
• Work stealing scheduler — Automatic load balancing
• Rust-inspired futures — Familiar patterns, Zig performance
• Scalable design — From embedded to servers

Reality Check

Zuki is in early development — APIs change, bugs exist, documentation is minimal.

The foundation is solid and performance is already impressive. Good for:

• Learning async patterns in Zig
• Contributing to runtime development
• Exploring high-performance async

Not ready for production.

Quick Example

// Create an async task
var delay = DelayFuture.from_millis(&timer, 1000);
const task = Task.from_future(&delay, 1);

// Run it on the executor
var executor = try SingleThreadedExecutor.init(allocator);
try executor.spawn(task);
try executor.run();

Simple. No complexity, no overhead.

Architecture

What makes Zuki different:

• Lock-free MPMC queues — Multiple producers, multiple consumers, zero locks
• Intrusive linked lists — Zero-allocation data structures
• Atomic operations — Compare-and-swap for maximum throughput
• Work stealing — Tasks flow where needed
• Priority scheduling — Important tasks get priority

Documentation

• Getting Started — Start here
• Architecture Guide — How Zuki works
• Roadmap — What's planned
• Examples — Working code

Contributing

Zuki needs contributors who understand performance:

• Found a bug? Open an issue
• Want to contribute? Check CONTRIBUTING.md
• Have ideas? Start a discussion