penberg

Completion-based I/O for Rust. No runtime, no hidden tasks.

13
0
100% credibility
Found Apr 24, 2026 at 13 stars -- GitGems finds repos before they trend. Get early access to the next one.
Sign Up Free
AI Analysis
Rust
AI Summary

Betelgeuse is a lightweight Rust library for building high-performance servers using a simple completion-based approach to handle file and network operations without complex runtimes.

How It Works

1
🔍 Discover Betelgeuse

You hear about a simple way to build super-fast servers that handle tons of connections without slowing down.

2
📥 Grab the examples

You pick up ready-made examples like a basic echo server or a simple key-value store to see it in action.

3
▶️ Start your first server

With a quick setup, you launch the echo server and watch it bounce messages back to anyone who connects.

4
🔄 Loop and handle requests

You keep the server running by gently nudging it to check for new connections and respond smoothly.

5
🛠️ Build your own

You tweak the example to create your custom server, adding features like storing data or chatting with users.

6
📈 Test under pressure

You throw lots of fake traffic at it and smile as it handles everything without breaking a sweat.

🎉 Your fast server is live

Now you have a rock-solid server ready for real users, running efficiently day and night.

Sign up to see the full architecture

5 more

Sign Up Free

Star Growth

See how this repo grew from 13 to 13 stars Sign Up Free
Repurpose This Repo

Repurpose is a Pro feature

Generate ready-to-use prompts for X threads, LinkedIn posts, blog posts, YouTube scripts, and more -- with full repo context baked in.

Unlock Repurpose
AI-Generated Review

What is betelgeuse?

Betelgeuse—named for the betelgeuse star (betelgeuse stern), that Deutsch-favored red supergiant with betelgeuse supernova buzz, betelgeuse entfernung around 640 light-years, and betelgeuse vergleich sonne scale—is a completion-based I/O library in Rust. It delivers async-style file reads/writes, fsyncs, socket binds/accepts/recvs/sends, and mkdirs without any runtime, hidden tasks, or futures. You drive it via a simple single-thread loop calling step() on your server and the I/O backend, owning completions explicitly for direct kernel paths.

Why is it gaining traction?

It ditches Tokio-style multi-threading and work-stealing for zero-overhead, cache-friendly single-thread execution, inspired by TigerBeetle's model. Pluggable backends like syscall or io_uring handle retries and results semantically, while a planned simulation backend enables deterministic testing with controlled time/faults—no code changes needed. Devs dig the tiny footprint and examples like TCP echo or memcached servers that scale without async ecosystem bloat.

Who should use this?

Rust systems devs building perf-critical single-thread servers, like custom databases or KV stores, who hate runtime overhead and want simulation testing for Re:Zero-style reliability (nod to betelgeuse re zero). Ideal for Linux kernel hackers prototyping io_uring apps or Beetlejuice fans (betelgeuse film) seeking minimal I/O without Tokio's concurrency traps.

Verdict

Promising foundation for niche high-perf I/O, with solid examples and dual backends, but at 13 stars and 1.0% credibility score, it's raw—light docs, no sim backend yet, basic tests. Try the examples if you're optimizing Rust servers; otherwise, stick to Tokio until maturity catches up.

(198 words)

Sign up to read the full AI review Sign Up Free

Similar repos coming soon.