Service Runner: Simple Safe Modular

Functions as modules

Not everything deserves a struct. srvc ships five thin adapters that turn plain functions into modules. They are glue only: no options, no defaults, no logic of their own. Anything that wraps a real dependency belongs in a proper module, yours or one from go-srvc/mods.

package main

import (
	"context"

	"github.com/go-srvc/srvc"
)

func main() {
	srvc.RunAndExit(
		// Called during init, Run blocks until shutdown.
		srvc.InitMod("migrations", runMigrations),
		// Init and stop pair without any work of its own during run.
		srvc.IdleMod("cache", openCache, closeCache),
		// Called during run with a context that is canceled on shutdown.
		srvc.CtxMod("consumer", consume),
		// Called during run, service shuts down once it returns.
		srvc.RunMod("job", doWork),
		// Called during stop, in reverse order like any other module.
		srvc.StopMod("flush", flushBuffers),
	)
}

func runMigrations() error { return nil }
func openCache() error     { return nil }
func closeCache() error    { return nil }
func doWork() error        { return nil }
func flushBuffers() error  { return nil }

func consume(ctx context.Context) error {
	<-ctx.Done()
	return nil
}

RunMod and CtxMod run their function during the run phase and end the service when it returns; CtxMod cancels the context on Stop. InitMod, StopMod, and IdleMod have no run-phase work, so their Run blocks until shutdown. Stop order stays reverse of the module list.