Module 2 Flashcards
(46 cards)
the task of making disparate applications work together to produce a unified set of functionality
Enterprise integration
Integrated applications should minimize their dependencies on each other so that each can evolve without causing problems to the others.
APPLICATION COUPLING
When integrating an application into an enterprise, developers should strive to minimize both changes to the application and the amount of integration code needed.
INTRUSIVENESS
Different integration techniques require varying amounts of specialized software and hardware.
TECHNOLOGY SELECTION
Integrated applications must agree on the format of the data they exchange.
DATA FORMAT
Integration should minimize the length of time between when one application decides to share some data and other applications have that data.
DATA TIMELINESS
Many integration solutions allow applications to share not only data but functionality as well, because sharing of functionality can provide better abstraction between the applications
DATA OR FUNCTIONALITY
Computer processing is typically synchronous—that is, a procedure waits while its subprocedure executes.
REMOTE COMMUNICATION
Remote connections are not only slow, but they are much less reliable than a local function call. When a procedure calls a subprocedure inside a single application, it’s a given that the subprocedure is available.
RELIABILITY
Integration Styles: Shared Databases
SQL - Structured Query Language
ODBC - Open Database Connect
JDBC – Java Database Connectivity
OLE-DB – Object Linking and Embedding Database
RDA - Remote Database Access
SQL
Structured Query Language
ODBC
Open Database Connect
JDBC
Java Database Connectivity
OLE-DB
Object Linking and Embedding Database
RDA
Remote Database Access
Shared Database: Advantage of Integration Style
Near-universal integration
System abstraction
System Decoupling
Ease of Integration
Shared Database: Disadvantage of Integration Style
Doesn’t work well with ORMs
Performance bottleneck issues
Schema change issue
Data Ownership
Integration Styles: Messaging
JMS – Java Message Service
MSMQ – Microsoft Message Queue
AMQP – Advanced Message Queuing Protocol
SNS – Amazon Simple Notification Service
SQS – Amazon Simple Queue Service
STOMP – Simple Text Oriented Messaging Protocol
SMPP – Short Message Peer-to-Peer – SMS Messaging
MQTT – MQ Telemetry Transport – M2M/IOT Messaging
JT/400 – AS400 Data Queue
JMS
Java Message Service
MSMQ
Microsoft Message Queue
AMQP
Advanced Message Queuing Protocol
SNS
Amazon Simple Notification Service
SQS
Amazon Simple Queue Service
STOMP
Simple Text Oriented Messaging Protocol