DEV Community

Tosiiko
Tosiiko

Posted on

I built Wetask: a unified runtime for distributed tasks, scheduling, and caching

#go #devops #distributed #release

Today I’m releasing Wetask v0.1.0-rc.1, the first public release candidate of a system I’ve been building in Go.

Wetask combines several backend responsibilities into one deployable runtime:

  • Distributed task execution
  • Scheduled jobs
  • Integrated caching
  • Durable queue recovery
  • High availability and leader election
  • Health checks, metrics, administration, and operational tooling

The goal is straightforward: reduce the number of separate components teams need to operate for background jobs, scheduling, caching, and failover.

Current release status

This is a controlled pilot release candidate, not yet a general-availability enterprise release.

The release includes compiled binaries for:

  • Linux amd64 and arm64
  • macOS Intel and Apple Silicon
  • Windows amd64

The implementation source remains private. The public repository contains only compiled releases, installation tooling, checksums, licenses, and package metadata.

Install Wetask

On macOS or Linux:


bash
curl -fsSL https://raw.githubusercontent.com/tosiiko/wetask-releases/main/install.sh \
  | sh -s -- --yes --version v0.1.0-rc.1
Enter fullscreen mode Exit fullscreen mode

Top comments (1)

Collapse
 
tosiiko profile image
Tosiiko •

The installer detects the operating system and architecture, downloads the appropriate archive, and verifies its SHA-256 checksum before installation.
You can also download the archives directly:
github.com/tosiiko/wetask-releases...
Reliability work
Before this release, I ran unit, integration, race, chaos, upgrade, recovery, load, and direct client-pipeline tests.
The direct gRPC pipeline benchmark processed 8,991,000 mixed cache operations with zero client errors. Peak throughput reached approximately 753,000 operations per second in a container-local benchmark.
I also fixed and regression-tested a lock-order deadlock affecting concurrent durable task submission and result waiting.
What comes next
The next milestones are:
A dedicated Homebrew tap
Multi-architecture container publishing
Secured three-node staging validation
Live failover and restore exercises
Feedback from controlled production pilots
If you test Wetask, installation problems and reproducible binary issues can be reported through the public repository. Please use private vulnerability reporting for security issues.
Release:
github.com/tosiiko/wetask-releases...
I’d especially value feedback from teams operating task queues, schedulers, caching systems, or combinations of those components.