Constraints: the ChatOps Webex notifier must scale and release independently from the inventory UI; one small team owns a separate batch reporter with a single weekly change window. Which pairing of official patterns best matches?
Select an answer to reveal the explanation.
Short Explanation
Match the tool to the job: independent scale and release push you toward microservices or SOA; one team and one window point back to a monolith. Event-driven is extra when producers must not block—not a blanket stamp for every box.
Full Explanation
Architectural patterns are chosen from constraints. Independent scale/release between ChatOps notifier and inventory UI supports microservices or coarser services-oriented design. A small team with one change window justifies a monolith for that reporter. Event-driven applies when decoupling producers from consumers is required; it is not mandatory for every component.