Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: None
-
Labels:
-
Sprint:Arch 2018-09-24
-
Team:Architecture
Description
The “Data Management Control System” sounds like a key service which, one might assume, orchestrates the whole of Data Management. I've heard various highfalutin claims about what the DMCS might do.
In fact, I understand (based on LDM-152) that it's a tightly scoped part of the ingest system. That's fine, but, in an attempt to avoid future confusion, it'd be nice if LDM-148 made this clear.
Attachments
Activity
Will discuss with John Swinbank.
Informally reviewed with John Swinbank and James Parsons. Merged to master, RFC-530 submitted.
Part of the confusion is that the role has changed. The "DMCS" used to refer to a component that was a master controller for all DM activities within a site. That component no longer exists, per se. The component that is currently labeled as "DMCS" is an internal software component shared by a number of services running in the Prompt Base Enclave. As an internal component, I'm not sure it deserves a place in LDM-148, which is primarily describing services. I could mention it in the Middleware section, but then I'd also logically have to describe the many other components of those services that operate at a similar level.