Featurewise

Featurewise organisation

Building online services around the things they do.

Features are the core

The things your software does are its features: commands, queries and workers. They live in the core.

Entrypoints invoke them

APIs, UIs, MCP servers, queue workers and schedulers are entrypoints. Entrypoints know about the core; the core never knows about them.

Links are potential invocations of features

An object naming a feature and containing its arguments: that is a link. Links are made in the core, and each response offers the ones the caller can follow next. A service is usable and well-mannered before a UI exists. A UI is a light dressing for a service.

Made for agents too

Those same links tell an agentic client what it can do next, and offer only what would work for it now.

One vocabulary

Features give everyone the same names for what the service does. CancelSend is a class in the code, the subject of its tests, a line in the logs, and what the product owner calls it when someone wants a message back.

A diagram of a message outbox's features, each drawn as a toy boat: Compose links to Send, Send to Messages, CancelSend and itself, and through a queue to ActuallySend, a worker; Messages links to Compose and CancelSend, and CancelSend back to Messages.
Features implementing a message outbox: each feature is a boat, each link an arc. Send puts a job on a queue, so the message can still be cancelled.

Try the demosThe book

From the blog

  1. The book is in development

    Featurewise Organisation is being written. Here's what it's about, and its provisional contents.