definition basics part 1 Flashcards
Interoperability
ability of 2 application systems to exchange information with each other and to use the information that has been exchanged
Legacy systems
Best of breed policy
Vendor lock-in
Weak IT governance
Application integration
more or less as interoperability, but interoperability stresses exchanging, rather than combining
APIs
set of functions and procedures that specify how software components should interact
Screen scraping
Robotic process automation (RPA)
Loosely coupling
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
Service providers
provide a service that preforms some business function at the request of the service consumer
Service consumers
developers do not have to design, build or test services; they just use them to accomplish business functions
Service registries
provide a mechanism for storing. Managing and accessing service contracts.
Middleware
any type of software that facilitates communication between 2 or more software systems.
Remote procedure call (RPC)
procedure call over network; network hidden for programmer
Message-oriented middleware (MOM)
like RCP, but asynchronous: messages are queued
Database-oriented
facilitates communication with databases
Application servers
container for web applications
Integrating the Healthcare Enterprise (IHE)
International platform for healthcare and software providers, IT professionals, and governments to promote interoperability
IHE connectathons
Encoding (in SOAP)
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.)
simple values
the values of built-in types from XML schema part 2 or enumeration or byte array
Compound values
constructed as a composite of several parts, each with a type and can be of struct or arrays or complex type
WSDL
industry-agreed-upon XML language that can be used to describe web services.
Web service
A software system that allows applications to communicate over a network using standard protocols.
SOAP (WS-*) web services
A standardized web service protocol that ensures secure, reliable, and transactional communication.
RESTful web services
A lightweight, flexible architecture for web services based on standard HTTP methods (GET, POST, etc.).
WSDL (Web Services Description Language)
XML-based language that describes what a SOAP web service does and how it can be accessed.
Swagger (OpenAPI specification)
A framework for describing RESTful APIs in a machine-readable format.
UDDI (Universal Description, Discovery and Integration)
A now-deprecated registry for finding and describing web services. -> Allowed businesses to publish and discover SOAP services.
SOA (service oriented architecture)
A software design pattern where applications provide services to other applications via a network. -> Encourages loose coupling, reusability, and standard interfaces.
Microservices
An architectural style where applications are built as small, independent services.
WS- (WS-ReliableMessaging, WS-Security, etc.)*
A set of XML-based enterprise standards that add security, reliability, and transactions to SOAP services. -> Preferred for complex enterprise integrations.
