Go like Rails for one API service.

The line

Every app rides the same four stops.

Rails gives you Active Record, Action Controller and friends. Bogie gives you the same separation, spelled out in plain Go. Here is what bogie g scaffold post lays down, plus a job from bogie g job.

1. 01 · app/domain · db/queries · app/models

   Models keep the SQL honest

   A domain type with no third-party imports. Named queries in plain SQL, compiled by sqlc onto pgx. A store maps one to the other, and runs the model's validations on save. When you want to know what hits the database, you open a .sql file.

   // app/domain/post.go
   type Post struct {
   	ID          string
   	Title       string
   	Body        string
   	Score       int32
   	PublishedAt time.Time
   	AuthorID    string
   	CreatedAt   time.Time
   	UpdatedAt   time.Time
   }

   -- db/queries/posts.sql
   -- name: CreatePost :one
   INSERT INTO posts (title, body, score, published_at, author_id)
   VALUES ($1, $2, $3, $4, $5) RETURNING *;

2. 02 · app/controllers

   Controllers convert and call

   A handler converts HTTP into domain values, calls one method on a store interface declared next to it holding only what that controller needs, and converts the result back. *gin.Context never leaves this folder.

   // app/controllers/posts_controller.go
   type postsStore interface {
   	CreatePost(ctx context.Context, p domain.Post) (domain.Post, error)
   	GetPost(ctx context.Context, id string) (domain.Post, error)
   	ListPosts(ctx context.Context, limit int32) ([]domain.Post, error)
   	UpdatePost(ctx context.Context, p domain.Post) (domain.Post, error)
   	DeletePost(ctx context.Context, id string) error
   }

3. 03 · app/views

   Views are the wire contract

   A domain type never doubles as a wire type, so a field added to the database does not silently appear on the wire. Requests and responses are their own structs.

   // app/views/posts.go
   type PostResponse struct {
   	ID          string    `json:"id"`
   	Title       string    `json:"title"`
   	Body        string    `json:"body"`
   	PublishedAt time.Time `json:"published_at"`
   }

4. 04 · app/jobs · bogie g job

   Jobs can commit with the row

   River runs on the same Postgres as the app: no Redis, no second system to keep up. Enqueue with InsertTx inside a transaction and the job commits with the row or not at all. bogie g job registers the worker above the bogie:jobs marker.

   type SendWelcomeArgs struct{}
   
   func (SendWelcomeArgs) Kind() string { return "send_welcome" }
   
   type SendWelcomeWorker struct {
   	river.WorkerDefaults[SendWelcomeArgs]
   	Log *slog.Logger
   }
   
   func (w *SendWelcomeWorker) Work(ctx context.Context,
   	job *river.Job[SendWelcomeArgs]) error {
   	w.Log.InfoContext(ctx, "send_welcome: not implemented yet", "job", job.ID)
   	return nil
   }