Architecting energy-first: when the constraint changes the design

Add a new non-functional requirement and the design changes. Make energy one of them, and a surprising thing happens: many systems get simpler, because the flashiest architecture is rarely the most efficient one.

Question the event storm

Event-driven everything can be elegant — and profligate. Each hop through a broker is serialisation, network and compute. When energy is on the table, we ask whether a direct call or a batched job would do the same work for a fraction of the power.

Place workloads with intent

Where compute runs matters as much as how much runs. Edge, region and hardware generation all move the carbon number. Energy-first architecture treats placement as a design decision, not an ops detail.

Constraints are not the enemy of good design. They are usually the reason it exists.

The reward for taking energy seriously early is a system that is not only greener, but easier to reason about and cheaper to run.