Integration Infrastructure (iHub)

image of  old-fashioned machinery

We provide "iHub" as an iPaaS1 customized to fit Berkeley's particular and varied needs and centrally funded to promote the evolution of campus IT to a more agile, secure, service-based digital environment.

The iHub is a prime example of aspect oriented2 architecture, centralizing common, cross-cutting functions from those that support specific business concerns. iHub fulfills the non-functional requirements of integration services, such as physical and network security management, automated CI/CD3, logging, notification, transaction management, exception management, etc. This enables integration architects and developers to build services faster, more reliably, and in closer concert with their functional counterparts. 

1 Integration Platform as a Service provides a loosely-coupled interface between different systems either in the cloud or on premises.

2 Aspect-oriented design seeks to modularize systems in order to isolate secondary or supporting functions from primary business logic. AOD allows these concerns to be expressed separately and shared, then automatically gathered and unified into working systems.

3 Continuous Integration and Continuous Deployment bridges the gaps between development and operation activities and teams by enforcing automation in building, testing and deployment of applications.