Module 2 Flashcards

(46 cards)

1
Q

the task of making disparate applications work together to produce a unified set of functionality

A

Enterprise integration

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Integrated applications should minimize their dependencies on each other so that each can evolve without causing problems to the others.

A

APPLICATION COUPLING

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

When integrating an application into an enterprise, developers should strive to minimize both changes to the application and the amount of integration code needed.

A

INTRUSIVENESS

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Different integration techniques require varying amounts of specialized software and hardware.

A

TECHNOLOGY SELECTION

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Integrated applications must agree on the format of the data they exchange.

A

DATA FORMAT

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Integration should minimize the length of time between when one application decides to share some data and other applications have that data.

A

DATA TIMELINESS

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

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

A

DATA OR FUNCTIONALITY

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Computer processing is typically synchronous—that is, a procedure waits while its subprocedure executes.

A

REMOTE COMMUNICATION

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

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.

A

RELIABILITY

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Integration Styles: Shared Databases

A

SQL - Structured Query Language
ODBC - Open Database Connect
JDBC – Java Database Connectivity
OLE-DB – Object Linking and Embedding Database
RDA - Remote Database Access

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

SQL

A

Structured Query Language

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

ODBC

A

Open Database Connect

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

JDBC

A

Java Database Connectivity

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

OLE-DB

A

Object Linking and Embedding Database

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

RDA

A

Remote Database Access

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Shared Database: Advantage of Integration Style

A

Near-universal integration
System abstraction
System Decoupling
Ease of Integration

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Shared Database: Disadvantage of Integration Style

A

Doesn’t work well with ORMs
Performance bottleneck issues
Schema change issue
Data Ownership

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Integration Styles: Messaging

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

JMS

A

Java Message Service

20
Q

MSMQ

A

Microsoft Message Queue

21
Q

AMQP

A

Advanced Message Queuing Protocol

22
Q

SNS

A

Amazon Simple Notification Service

23
Q

SQS

A

Amazon Simple Queue Service

24
Q

STOMP

A

Simple Text Oriented Messaging Protocol

25
SMPP
Short Message Peer-to-Peer – SMS Messaging
26
MQTT
MQ Telemetry Transport – M2M/IOT Messaging
27
JT/400
AS400 Data Queue
28
Messaging: Advantage of Integration Style
Highly decoupled systems Guaranteed delivery Async communications Broadcast capabilities Ease of scalability
29
Messaging: Disadvantage of Integration Style
Integration beyond firewall Implementation complexity Testing complexity Cross platform standards Async error handling
30
Integration Styles: Remote Procedure
REST – Representational State Transfer SOAP – Simple Object Access Protocol RMI – Remote Method Invocation CORBA – Common Object Request Broker Architecture Websockets – Hixie, Hybi, RFC/Request for Comments CGI – Common Gateway Interface
31
REST
Representational State Transfer
32
SOAP
Simple Object Access Protocol
33
RMI
Remote Method Invocation
34
CORBA
Common Object Request Broker Architecture
35
Websockets
Hixie, Hybi, RFC/Request for Comments
36
CGI
Common Gateway Interface
37
Remote Procedure: Advantage of Integration Style
Data encapsulation and ownership External systems integration Mature frameworks and tools
38
Remote Procedure: Disadvantage of Integration Style
Tight system coupling Async communications Broadcast capabilities
39
Integration Styles: File Transfer
FTP/SFTP – File Transfer Protocol HDFS – Hadoop Distributed File System SCP – Secure Copy Protocol SMB – Server Message Block CIFS – Common Internet File System
40
FTP/SFTP
File Transfer Protocol
41
HDFS
Hadoop Distributed File System
42
SCP
Secure Copy Protocol
43
SMB
Server Message Block
44
CIFS
Common Internet File System
45
 File Transfer: Advantage of Integration Style
Universal Integration Style Integration Simplicity System Abstraction
46
File Transfer: Disadvantage of Integration Style
Error Processing Data Synchronization Timeliness Data-only Transfer