Univ of Hawaii - ITS Technical Architecture - Brick
...
Integration Use-Cases & Factors | MB | API/WS | DB | Batch ETL |
| Yes | No(2) | No(2) | No |
| Yes | Yes | Yes | Yes |
| Yes | Yes | Yes | Yes |
| Yes | No | No | Yes |
| Yes | No | No | No(4) |
| No | Yes(6) | Yes(5) | No |
| No | Yes | Yes | No |
| No(1) | No(3) | Yes | Yes |
Table footnotes:
This is relatively new technology for our community. It has been introduced via the UH App Developer meetings and IAM documentation for developers. HCC, ORS, MIS and IAM thus far have become familiar with the MB.
Brokered event-triggered data synchronization can be considered near real-time and scalable. Direct high frequency polling of an application is not scalable and is not recommended.
Writing custom APIs, while not difficult, is not a typical programming task.
Batch ETLs tend to be written one per pair of applications.
However, it is unusual for another application to update the data of a System of Record.
Yes, if the API/WS is designed accordingly. The API/WS decides what’s considered to be a transaction, not the consumer application.
Experimental |
|
Strategic (3-5 Years) |
|
Tactical (1-2 Years) |
|
Containment |
|
Retirement |
|
Notes
The UH Message Broker is in Production for the following:
Banner, message producer
HCC, message consumer
KFS, message consumer
myGrant, message consumer
SECE, message producer
UHIMS, message producer and consumer
...