Infrastructure terms, defined properly

A node that retains historical state at every block height.

Dedicated physical servers without a virtualisation layer between you and the hardware.

A batch of transactions appended to the chain.

The mechanism by which network participants agree on the canonical chain.

Shifting traffic from a failed component to a healthy one.

The point at which a block can be considered irreversible.

A node that validates every block and keeps recent state.

A design where component failure does not cause service failure.

Identity and access management for humans and machines.

A service that transforms raw blocks into queryable application data.

Managing infrastructure through versioned declarative configuration.

The time between a request and its response.

A component that distributes requests across a pool of backends.

The production network where transactions carry real value.

Infrastructure deployed across more than one geographic region.

A storage interface for solid state drives offering low latency and high parallelism.

The ability to understand system state from its external outputs.

A reorganisation where previously accepted blocks are replaced by a different chain.

The API interface applications use to read from and write to a blockchain network.

A network used for testing infrastructure and applications without real value at stake.

The volume of work a system handles per unit of time.

A node that participates in consensus and carries key material with economic consequences.

An access model where no request is trusted based on network location alone.