Identify One Service Candidate

Identify One Service Candidate

animation
soa
design-patterns

Try It Yourself

Apply the boundary test to a system you know. Write down the evidence for your choice.

Write one clear boundary. Name its input, output, owner, store, and safe failure. Keep its data behind that owner. Then test a caller that is slow, a store that is down, a repeated event, and a partial update. Record what retries, what waits, and what a user sees. Compare this with one well-cut part in a single app before you split it across the network.

Try the boundary with a paper event. A device reports high heat. The intake part checks the message. The rule part decides to warn. The notice part contacts a person. Write who owns each record. Write what happens if the next part is down. Keep the first accepted fact safe. Let later work retry without making the same alert many times.

Choose an IoT platform or project you know and write a short extraction rationale.

  1. Name one candidate capability, such as telemetry ingestion, device registry, command dispatch, or notifications.
  2. List the data it owns and the data it needs from other domains.
  3. Identify its consumers: devices, dashboards, analytics, partners, or other services.
  4. Decide whether collaboration should be synchronous API, asynchronous event, or both.
  5. Write the reason to extract it, or write why it should stay inside the modular monolith.
  6. Define one metric that would prove the extraction helped.

Back to the chapter