Digitized historical permits sit in archives, while the live permitting system emits events as filings occur. How should product owners treat those sources?
Select an answer to reveal the explanation.
Short Explanation
Old scanned permits are the attic boxes; live filing events are the doorbell. Both are useful, just for different chores. Batch history and live streams are not the same source mode.
Full Explanation
Historical batch archives and live operational event feeds serve different application needs. Digitized permits support longitudinal analysis; live permitting events support current workloads and monitoring. Product owners should not collapse them into one Velocity assumption. Correct mode labeling improves architecture and SLA choices for civic permitting services.
Treating them as identical feeds that always share the same Velocity fails by concept: batch history and live events differ. Claiming live events make archives useless fails by concept: longitudinal analysis still needs history. Calling both person-to-person only communications with no systems involved fails by concept: permitting systems emit and store these modes.
Exam caveat: Treat historical batch versus live event streams as different source modes for different applications—do not equate Velocity or discard archives.
Operational check: Label archive and live permitting sources separately in the catalog, assign distinct freshness SLAs, and route longitudinal vs operational apps to the matching mode. Document residual risk for civic operators and revisit after the next production change window. Confirm owners, SLAs, and rollback criteria in the runbook before go-live.