4. Consumer first: consumer first is about making it as simple and easy as possible for the consumers of an MS to successfully use it. 5. Infrastructure agnostic: MS must be portable and elastic. Moving a service across hosts, datacenters, or clouds should not be a problem. They should not be dependent on static addresses or ports when possible. 6. Automation: automation applies to all aspects of an MS. Automation means embracing DevOps and continuous integration and delivery processes (CI/CD). Discoverable: since MS are auto deployed and infrastructure agnostic, they are required to be dynamically discoverable. Consumers must have the ability to query a service registry to lookup available instances and then route accordingly. 8. Lightweight communications: MS must follow a dumb pipe, smart endpoint approach for communication protocols. The core requirement is that no business logic be implemented within the protocol or broker and all domain logic remain within the service endpoint implementations themselves. 9. Highly resilient: building applications as a cohesive set of services requires the ability to tolerate and gracefully handle failures of all kinds. 10. Highly observable: provides insight and understanding of how request paths are processed and flow across services. Since large applications consist of many distributed services there is a need to collect, aggregate, and analyze logs and metrics across all services. These MSs principles can be measured using different paradigms. One example being a metal rating (platinum, gold, silver, and Bronze) in which the rating reflects the percentage of match of the MS to the principles described above. Within the analytics framework, we leverage the term "microservice" to describe a reusable, open analytic solution that provides useful output(s) and offers input APIs to control common data, computation, and control parameters. The DCAE analytics and collection framework described previously includes a controller that enables management and health checks of both ana