When you have no state, you can have any number of machines handling requests from any number of consumers and not care what consumer is making what request of what machine or in what order.
So aside from session validation across a pool, can you really keep every call completely stateless? If your API does not, what issues does this reveal about coupling and dependencies within your workflow?
