definition basics part 1

Question 1

Interoperability

Answer 1

ability of 2 application systems to exchange information with each other and to use the information that has been exchanged

Question 2

Legacy systems

Question 3

Best of breed policy

Question 4

Vendor lock-in

Question 5

Weak IT governance

Question 6

Application integration

Answer 6

more or less as interoperability, but interoperability stresses exchanging, rather than combining

Question 7

APIs

Answer 7

set of functions and procedures that specify how software components should interact

Question 8

Screen scraping

Question 9

Robotic process automation (RPA)

Question 10

Loosely coupling

Answer 10

the internals of an application or business service must be able to change without impacting client applications. Specifically, a service consumer should not be required to know any more about service than what is contained in the published contract

Question 11

Service providers

Answer 11

provide a service that preforms some business function at the request of the service consumer

Question 12

Service consumers

Answer 12

developers do not have to design, build or test services; they just use them to accomplish business functions

Question 13

Service registries

Answer 13

provide a mechanism for storing. Managing and accessing service contracts.

Question 14

Middleware

Answer 14

any type of software that facilitates communication between 2 or more software systems.

Question 15

Remote procedure call (RPC)

Answer 15

procedure call over network; network hidden for programmer

Question 16

Message-oriented middleware (MOM)

Answer 16

like RCP, but asynchronous: messages are queued

Question 17

Database-oriented

Answer 17

facilitates communication with databases

Question 18

Application servers

Answer 18

container for web applications

Question 19

Integrating the Healthcare Enterprise (IHE)

Answer 19

International platform for healthcare and software providers, IT professionals, and governments to promote interoperability

Question 20

IHE connectathons

Question 21

Encoding (in SOAP)

Answer 21

a set of rules of how to express application-defined data types on the wire in XML form.
(refers to how data types are represented in XML format when being transmitted.)

Question 22

simple values

Answer 22

the values of built-in types from XML schema part 2 or enumeration or byte array

Question 23

Compound values

Answer 23

constructed as a composite of several parts, each with a type and can be of struct or arrays or complex type

Question 24

WSDL

Answer 24

industry-agreed-upon XML language that can be used to describe web services.

Question 25

Web service

Answer 25

A software system that allows applications to communicate over a network using standard protocols.

Question 26

SOAP (WS-*) web services

Answer 26

A standardized web service protocol that ensures secure, reliable, and transactional communication.

Question 27

RESTful web services

Answer 27

A lightweight, flexible architecture for web services based on standard HTTP methods (GET, POST, etc.).

Question 28

WSDL (Web Services Description Language)

Answer 28

XML-based language that describes what a SOAP web service does and how it can be accessed.

Question 29

Swagger (OpenAPI specification)

Answer 29

A framework for describing RESTful APIs in a machine-readable format.

Question 30

UDDI (Universal Description, Discovery and Integration)

Answer 30

A now-deprecated registry for finding and describing web services. -> Allowed businesses to publish and discover SOAP services.

Question 31

SOA (service oriented architecture)

Answer 31

A software design pattern where applications provide services to other applications via a network. -> Encourages loose coupling, reusability, and standard interfaces.

Question 32

Microservices

Answer 32

An architectural style where applications are built as small, independent services.

Question 33

WS- (WS-ReliableMessaging, WS-Security, etc.)*

Answer 33

A set of XML-based enterprise standards that add security, reliability, and transactions to SOAP services. -> Preferred for complex enterprise integrations.