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
Integration Processes
Architectural Standards
Enterprise Integration Methodology
Patterns
APIs
Security
Messaging
- Confluent Platform - Confluent Platform leverages Apache Kafka, open source technology, which acts as reatime, fault tolerant, highly scalable messaging system.
Documentation
- API Portal