Goer documentation

A guide to systems that keep going.

If you build services in Go, you know the feeling: one thing breaks and suddenly everything’s on fire. These docs are about a different way to build, where a broken piece gets restarted and the rest carries on. Goer is an experiment, and we’ll be straight with you about what works and what doesn’t.

The main word to know is process (some people say actor). It’s one small worker that keeps its own data and reads its own inbox. The docs come in four layers, and each one only needs the one before it: get something running, find out what’s underneath, look up exact spellings, then learn to watch it live.

Two kinds of code show up here. Your regular Go code imports goer and calls goer.NewSystem() (or lets the goer command do that for you). The process code is written in imgo, a cut-down Go, in files marked //go:build goer. There’s also a lower-level goer/runtime package for when you need it.