Building-permit review and fee-collection microservices must scale…

Question

Building-permit review and fee-collection microservices must scale independently, keep each task until success or dead-letter, and avoid losing work if one side slows. Which Domain 3 service best fits that decoupling?

Accepted Answer

OCI Queue, so producers and consumers scale independently with durable messages and DLQ isolation for failures. — When two city desks must not drop a form between them, use a durable inbox. Queue keeps the task until delete, and a DLQ isolates poison messages. Always-on HTTP or a click firehose solves different problems.

Answer

OCI API Gateway alone, because always-on HTTP between services never needs a durable inbox.

Answer

OCI Streaming alone, because every discrete task must be a replayable click-firehose log.

Answer

OCI Events alone, because bucket landing rules are the only supported microservice task bus.

Building-permit review and fee-collection microservices must scale independently, keep each task until success or dead-letter, and avoid losing work if one side slows. Which Domain 3 service best fits that decoupling?

Short Explanation

Full Explanation