 onboard their MS (i.e., analytics application) to the runtime platform A DCAE catalog: The metadata in the DCAE catalog will enable users of the DCAE analytics frame- work to rapidly discover data elements/metrics/datasets and will allow them to define and share datasets with other analytics users; this component may also provide meta- data necessary to enable orchestration of DCAE analytics framework (AF) MSs A goal of this solution is to ease development and deployment of real-time applications (e.g., closed-loop analytics, anomaly detection, capacity monitoring, congestion monitoring, alarm cor- relation, etc.) as well as other nonreal-time applications (e.g., analytics, forwarding synthesized or aggregated or transformed data to big data stores and other sorts of applications for monitoring network, VNF, and service health) to support the VNFs and services deployed in the network. Further, the intent is to structure the ecosystem such that agile introduction of applications from various providers can shorten the time required to move software from development through test and into production. It is expected that analytic applications are developed by various organizations, however, they all run in the DCAE analytics framework and are managed by the DCAE controller (see Chapter 7). 8.3.3 MS DESIGN PARADIGM MSs is a software architectural style in which large applications are composed from small loosely coupled services with independent lifecycles. This term has been popularized in the public domain by thought leaders such as Martin Fowler whose initial writings on MS architecture suggest that the goal of such service design is to build the system using a collection of services, using common core components, with strong public APIs to achieve these benefits: Easy to deploy new capabilities-often just a matter of instantiating a new MS Easy maintenance-services can often be independently upgraded with no impact of other services Easy decommissioning-tear down the service (assuming no further subscribers) Langua