The use of __________ services tends to __________ the size of service compositions.

Question

Options

• Aautonomous, increase
• Bstateless, decrease
• Cscalable, decrease
• Dagnostic, increase

• A
  6% (2)
• B
  75% (27)
• C
  14% (5)
• D
  6% (2)

Explanation

Stateless services minimize retained state between invocations, which maximizes their reusability across different compositions. Because a stateless service can be called by any consumer without worrying about prior session context, it can satisfy roles in multiple compositions - meaning a composition can leverage existing stateless services rather than requiring additional specialized or state-managing services, effectively keeping the composition smaller.

Why the distractors are wrong:

• A (autonomous, increase): Autonomous services are self-governing and loosely coupled, but autonomy is about independence from other services, not about how many services a composition needs - no direct size relationship.
• C (scalable, decrease): Scalability addresses capacity under load, not composition structure or the number of services involved in a workflow.
• D (agnostic, increase): This is the trickiest distractor and is actually partially true in SOA - agnostic (general-purpose) services do tend to increase composition size because their granularity means you need more of them to complete a specific business task. However, the question asks what decreases size, so D is the relationship to remember as a contrast, not the answer.

Memory tip: Link "Stateless → Smaller"** - dropping state baggage trims the composition. If you ever confuse it with agnostic, remember: agnostic services are general, so you need more of them (bigger), while stateless services are reusable, so you need fewer (smaller).

No community discussion yet for this question.