# Service Facts
Services are autonomous units of processing that communicate via messages and are composed of components.
# Services don't respond to queries
Services don't return data. They don't have
GET APIs, or respond to queries. Services process transactions. They do things. They aren't data access points. They receive instructions as messages and perform work. Services that can return data cause the services that request the data to loose their autonomy.
# Services don't fail when other services are unavailable
If a service that communicates with another service fails because the other service is unavailable, then the service is not autonomous. Services are autonomous. If a service isn't autonomous, then it's really not a service at all. A system of services that are not autonomous is not a service architecture. It's a distributed monolith.
# Services communicate by asynchronous messaging
Services receive commands, process those commands, and communicate the status of that processing by issuing events. A service that sends a command message to another service does not know the outcome of processing that command until the other service issues the resulting event and the originating service receives the event.
# Services are made of one or more autonomous components
Strictly-speaking, services are the infrastructural machinery that sits between the operating system and the service's business logic. The business logic itself is housed in a component. The service infrastructure provides consumers of inbound messages and dispatches the messages to a component's handlers. The handlers then interact with the component's entity (or entities) and outputs other messages in response. The combination of entities and handlers are where the business logic resides. Services may host one or more components. The term service is often used interchangeably with component. While this isn't strictly and technically accurate, it's a common informal way of speaking about services and components. The informal ambiguity is especially conspicuous when the service hosts only a single business component.
# The word "service" can refer to something logical or physical
The word "service" can refer to something logical or physical. Getting them confused can lead to misunderstandings that weaken the necessary separation between services and between components. When used to refer to something physical, the word "service" refers to the infrastructural machinery that sits between the operating system and the business component logic. When used logically, service can represent a number of physical services that are related to a single business function. Which meaning is being employed depends on context.
# Services represent business processes
A service is an implementation of a business process. Services cooperate together in more elaborate business processes. Services track the multiple steps in a process, receiving commands and events from other services or applications, and advancing to the next step based on the outcome of that processing.
# Services are state machines
The core logic of a service is structured as a state machine. The state machine entity gathers the data from various commands and events that the service processes, and informs the surrounding business logic about what steps in the process that the service implements to take next.
# Services are not APIs around data entities
A common misconception is that services are APIs wrapped around traditional data entities. This perspective is the result of seeing services as typical web APIs without realizing that services are more appropriately modeled as processes and state machines. An entity service is an antipattern that is the chief cause of ending up with a distributed monolith rather than a service architecture. In a service architecture it's unlikely that the data of a traditional aggregate entity, like an Product with a name, a price, and a quantity-in-stock would be housed in the same service.
# Services are not apps
It's far too easy to fall into the trap of presuming that the knowledge and skills acquired while building apps will apply to service design, development, and operations. Services and apps are opposite ends of the architectural spectrum. Failure to recognize this may lead you to implement apps while believing that you're implementing services. Apps may use (or be applications of) services, but the opposite is not true. Apps are about UIs, querying databases, formatting and displaying data, accepting form inputs, and a host of other user-interactive concerns. Services process commands. When a service has finished processing commands, it emits events that tell of the processing of the command. Services are not user-interactive. Services are largely batch-mode and asynchronous, while apps are interactive and synchronous. Apps are in the service of users. Services are in the service of apps (and other services). Any resemblance between apps and services is purely a matter of misinterpretation.