CSPA Workshop Hackathon June 22, 2016

Problem statement How to build an environment to support statistical production utilizing CSPA Single service != statistical process

Options Point to point integration Centralized orchestration “Smart services”

Point to Point Integration Effort / Logic Classification service Web Collection service Validation service Manual editing Service n System for subject 1 System for subject 2

Centralized orchestration Effort / Logic Classification service Web Collection service Validation service Manual editing Service n Orchestration engine Service Bus System for subject 1 System for subject 2

“Smart Services” Message broker Effort / Logic Classification service Web Collection service Validation service Manual editing Service n Message broker

Point to point integration Centralized orchestration “Smart Services” Benefits Low initial cost Centralized governance Control over orchestration Loose coupling High reusability Choreography instead of Orchestration Agile Problems Increased cost and complexity with many integrations Business logic / Orchestration logic in each application High cost of maintenance Low agility Risk of single point of failure Business logic in the transport layer Higher architectural complexity Less proven for Statistical production Different way of thinking Mitigation actions Standardize service contracts Standardize the client software Use it for the right thing Careful with vendor specific functionality Need to train people Governance on development of services

Point to Point Integration - Cost over time Loss Cost New pattern for communication Gain Point to point Number of connections

Next steps Is CSPA LIM complete enough? What are the consequences of the different options in regards to granularity and patterns Migration path CSPA IG should extend guidance Prototypes / Reference environment