Enterprise Integration

Objectives

• To define the framework and direction for the architecture and design efforts of all projects on the integration roadmap

• Provide ‘tools’ for traceability from business and IT objectives through architecture to implementation.

• Provide a common vocabulary to communicate overarching Integration Architecture principles and direction across multiple communities within Columbia University including integration teams, web services, academic applications, PeopleSoft and SIS development teams, IT management and business groups.

• Provide the means against which to measure architectural compliance of the work product from the various Columbia University IT teams chartered to produce integration solutions.

• Provide guidance for building the Columbia University Integration Platform consisting of COTS solution (will be selected via RFP).

• Define the Columbia University Integration Reference Architecture

Integration Strategy

1. API Strategy (published Nov. 2016) 

   1. Draft next version (unpublished google doc)

Integration Processes

1. API - InTake Process

2. API - Process Flow

Architectural Standards

Enterprise Integration Methodology

Patterns

1. /wiki/spaces/CUITEA/pages/60130251

2. /wiki/spaces/CUITEA/pages/60130204

3. CQRS

4. Event Sourcing

5. Database per Service

6. Saga

APIs

1. Restful API - Best Practices

2. API Specification ({json:api} and OAS 3.0)

3. Schema Standards (json-schema.org)

4. API/Integration Domain Names

Security

1. OAuth 2.0 Protection Standard

   1. CU-STD-INTR-001: OAuth 2.0 Scope Standards: API Coarse-grained Authorization

Messaging

1. Confluent Platform - Confluent Platform leverages Apache Kafka, open source technology, which acts as reatime, fault tolerant, highly scalable messaging system.
   
   

Integration Templates

1. Interface Specification Template

2. Data Mapping Template

Resources