The art of integration is linking systems together in ways that promote rather than hamper agility.
Different domains on campus control system functionality and data and offer their own specific capabilities. Integration technologies can orchestrate these distributed capabilities into seamless, unified business processes and user experiences. Leveraging these technologies requires specialized knowledge and skill, as well as a broad adoption of a common integration architecture on campus.
Our domain-specific consulting is intended to provide guidance to system-of-record data providers as they seek to create, promote, and manage APIs, message queues, and emerging integration methods in the medium to long-term. We can review existing efforts and help map future plans with an eye towards ensuring relevance within the campus' overall architectural plans.
As the campus continues its efforts to practice Enterprise Architecture (EA), we are also uniquely positioned as a resource for designing and implementing a loosely-coupled, service-based environment for the campus as a whole. Our areas of expertise include developing and managing solutions based on APIs and message queues, designing services to model the capabilities of data domains, and enabling centralized security and fine-grained authorization.
We serve the needs of projects with clear Associate CIO sponsorship, engaging with the functional and technical project leads to provide in-depth support during the planning and design stages of integration solutions. Together, we explore the considerations involved in integration architecture and design—and understand their campus-wide implications.
We help clients address the following integration service design questions:
- What services are needed, what are the common service styles, and what is the best style to be used for each use case?
- How can client applications and services communicate?
- How can a service be discovered and explored?
- How must services be designed to support evolving business logic without forcing clients to constantly change?
- What are the options for implementing service logic, and when should a particular approach be used?
- How can generic aspects like authentication, authorization, validation, caching, logging, and metering be supported centrally?
As needed by the project, we further undertake to develop APIs or messaging solutions resulting from the design work.