Multicellularity Through a Systems Architect's Eyes

Distributed systems also require identity, communication, division of labor and constraints that keep local behavior from destroying shared…

I approach multicellularity with an occupational habit: I want to draw boxes and arrows. That habit is useful because architecture forces questions about state, boundaries, interfaces, resources and failure. It is dangerous because natural systems were not designed to respect our diagrams.

Multicellularity requires cells to cooperate, specialize, exchange signals, regulate growth and suppress conflicts that would damage the collective. Development reconstructs this coordination again and again from a single starting cell.

Where does state live?

Software gives us the expectation that important state should have an owner. Natural systems often distribute state across structure, concentrations, relationships and history. A snapshot can therefore tell us less than the process that produced it.

Where are the interfaces?

Distributed systems also require identity, communication, division of labor and constraints that keep local behavior from destroying shared function.

Engineered interfaces are declarations. Natural boundaries are often material: membranes, tissues, ecological borders, channels, gradients or social conventions. They can leak, adapt and participate in the behavior they constrain.

What is the failure model?

Services in a cluster are designed modules. Biological cells are developmentally entangled, physically coupled and descended from reproductive lineages; their interests are not automatically identical.

Failure analysis is useful because normal operation hides assumptions. A healthy component can coexist with an unhealthy whole. A local optimization can damage the larger system. Robustness at one level can create fragility at another.

History is part of the architecture

Multicellularity evolved multiple times, making cooperation itself one of the major transitions in biological organization.

In a designed system, legacy structure may be accidental baggage. In an evolved or historically accumulated system, legacy structure can be the reason the current architecture exists at all. The path is not documentation around the system; sometimes it is part of the system.

The zoom test

A good architectural description should survive zooming. Going down a level should reveal mechanisms capable of implementing the higher-level pattern. Going up should reveal regularities that justify discussing the larger entity in its own vocabulary.

The phenomenon destabilizes the word individual: a body is one entity built from vast numbers of living cellular participants.

What turns a collection of living agents into one living individual?

Reading trail

These links are starting points for the scientific and historical ideas. The systems interpretation, analogies and conclusions here are my own.