stateless

Describes a component or service that keeps no data from one request to the next, so each request carries everything needed to handle it.

In more detail

Stateless does not mean the service forgets data: sessions and records still live in a database or store, and a cookie or token can point to them. It means any instance behind a load balancer can handle the next request, so the service scales out without coordination. Statelessness is also one of the constraints of REST.

Examples

The course's retry router picks the next topic from the record's attempt counter alone.
A Spring singleton service should hold only final references to other beans, never per-request data.

Related terms

Taught in

References

Certification courses