Tenta T^T Flashcards
XML Example
<?xml version=”1.0” encoding =”UTF-8”>
<bookstore>
<customer>
<firstname>John</firstname>
<lastname>Doe</lastname>
<email>johndoe@ex.com</email>
</customer>
<purchased_books>
<book>
<title>New Book</title>
<author>New Author</author>
<year>1999</year>
<price>99.00</price>
</book>
</purchased_books>
</bookstore>
XML Simple Example
Element
<?xml version=”1.0” encoding =”UTF-8”>
<bookstore>
<book>
<title>New Book</title>
<author>New Author</author>
<year>1999</year>
<price>99.00</price>
</book>
</bookstore>
XML Simple Example
Attribute
<?xml version=”1.0” encoding =”UTF-8”>
<bookstore>
<book category =”children”>
<title>New Book</title>
<author>New Author</author>
<year>1999</year>
<price>99.00</price>
</book>
</bookstore>
WSDL Root
Example
<definitions name=”BookOrder” targetNamespace=”http://bookstore.com/bookorder”
xmlns:tns=”http://bookstore.com/bookorder”
xmlns:xds=”….”
xmlns:soap=”….”
xmlns=”….”
>
……..
Abstract Message
Abstract PortType
Implementation binding
Implementation service
</definitions>
WSDL Abstract Message
Example
Root
<message name = “GetBookRequest”>
<part name = “parameters” element=”tns:BookRequest”/>
</message>
<message name = “GetBookResponse”>
<part name = “parameters” element=”tns:BookResponse”/>
</message>
Abstract PortType
Implementation binding
Implementation service
</definitions>
WSDL Abstract PortType
Example
Root
Abstract Message
<portType name=”BookPortType”>
<operation name=”operationBook”>
<input message=”BookRequest”/>
<output message=”BookResponse”/>
</operation>
</portType>
Implementation binding
Implementation service
</definitions>
WSDL Implementation binding
Example
Root
Abstract Message
Abstract PortType
<bindning name=”BookBinding” type=”http://bookstore.com/bookorder”>
<soap:binding style=”document” transport=”http://….”/>
<operation name=”operationBook”>
<soap:operation ….>
<input></input>
<soap:body use=”literal”/>
</input>
<output>
<soap:body use=”literal”/>
<output></output>
</operation>
**Implementation service**
</definitions>
</output>
WSDL Implementation service
Example
Root
Abstract Message
Abstract PortType
Implementation binding
<service name=”BookOrder”>
<port name=”BookPortType” binding=”tns:BookBinding”>
<soap:address location=”http://bookstore.com/bookorder”/>
</port>
</service>
</definitions>
3 evolutionary-first solutions for data sharing/integration
FTP (File Transfer Protocol)
Common DB
Sockets
FTP (File Transfer Protocol)
Non-real-time integration. A simple method where one application writes to a file that another application reads at a later time
Common DB
Non-real-time integration. Multiple applications read and write to the same database, enabling multipoint integration via SQL.
Sockets
Real-time integration. Communication between applications using websockets, allowing direct data sharing and real-time interactions
What is Linked Data?
Linked Data is a method for publishing and interconnection structured data on the web, based on four principles.
- Use URI (Unique Resource Identifier) as resource names
- Use HTTP URIs to look up data/URI
- Provide useful information using RDF format
- Include links to other related resources to create an interconnected data network
What is XML?
XML (Extensible Markup Language) is used to structure, store and transport data. Validation ensures that the document adheres to a specified XML schema (XDS).
What are its components? Why XML?
Root Node - The main node
Element Node -
Defines the structure of the data and can contain sub-elements
Attribute Node - Provides metadata for elements
Data Node - The actual content within an element or attribute
What is JSON?
JSON is a human-readable data exchange format that uses key-value pairs.
Ex
{
“customer”: {
“firstname”: ”John”,
“lastname”: ”Doe”,
“email”: “johndoe@ex.com”,
“purchased_books”: [
{
“title”: “New Book”,
“author”: ”New Author”,
“year”: 1999,
“price”: 99.00
}
]
}
}
Similarities between JSON and XML:
Used for Data Exchange - Both JSON and XML are widely used for structuring and exchanging data between applications
Human and machine readable - Both formats are readable by both humans and machines.
Hierarchical Data Representation - Both support nested (tree-like) structures.
Differences between JSON and XML:
Format: JSON used key-value pairs, whereas XML is based on tags
Readability: JSON is more compact and easier to read
Metadata: XML supports more metadata and complex structures
Performance: JSON is generally faster to parse due to its simpler syntax.
What is XDS?
XSD (XML Schema Definition) is a language used to define the structure of XML documents, specifying allowed elements, attributes, data types, and element order. XSD works as a framework that facilitates data validation.
What is RDF?
RDF (Resource Description Framework)
RDF (Resource Description Framework)
is a framework for describing relationships between resources on the web using a subject–predicate–object model.
What is RESTful and what are its three core elements?
RESTful (Representational State Transfer)
is an architectural style for building web services. Built on stateless operations that integrate using standardized HTTP methods.
Three core elements:
Resources – Represented as URLs.
Representation – Each request is independent.
Standard methods – Uses HTTP methods (GET, POST, PUT, DELETE).
What are Web Services?
Web Services allow different systems to communicate over a network using standardized protocols such as SOAP and REST. Uses HTTP for transmitting data.
What are Sockets?
Sockets enable real-time communication between applications through a network connection.
What is an API?
API (Application Programming Interface)
is a set of rules and specifications that software follows to communicate with other software. Acts as an interface between different systems, allowing them to interact with each other.
Advantages of loose and tight coupling
Loose coupling – Systems are less dependent on each other, providing higher flexibility
Tight coupling – Systems are highly interdependent, making integration more complex
What is SOA and its 5 design principles?
SOA (Service-Oriented Architecture)
is a design pattern where services communicate over a network.
Five design principles:
Loose coupling – Minimal dependency between services.
Reusability – Services can be reused in different systems.
Service contract – Each service has a defined API.
Composability – Services can be combined to form larger systems.
Autonomy – Services operate independently.
What is WSDL and its components?
WSDL (Web Services Description Language) is an XML-based format for describing web services.
Components of WSDL:
Types – Defines data types.
Message – Describes input and output data.
PortType – Defines operations.
Binding – Specifies protocols (e.g., SOAP or HTTP).
Explain IoT
IoT (Internet of Things)
refers to the connection of physical devices to the internet for data exchange.
Explain IoSI
IoSI (Internet of Service Integration)
refers to the integration of various services over the internet to enable seamless communication
What is MOM?
MOM (Message-Oriented Middleware)
is middleware that enables asynchronous message exchange between systems. Functions as an intermediate layer that sends, receives and manages data between different applications and systems, regardless of platform and language.
What is an RPC adapter?
RPC (Remote Procedure Call) adapter
allows programs to invoke functions on a remote server over a network, regardless of platform or programming language.
What are patterns and which (message) patterns exist?
Patterns are reusable solutions to common problems in system integration.
Examples of message patterns:
Request-Response
Publish-Subscribe
Point-to-Point
Event-Driven Messaging
Request-Response
When an application sends a message, how can it get a response from the receiver?
Send a pair of Request-Reply messages, each on its own channel.
Requestor -> Request -> Request Channel -> Replier - > Reply -> Reply Channel - Requestor
Publish-Subscribe
How can the sender broadcast an event to all interested receivers?
Send the event on a Publish-Subscribe Channel, which delivers a copy of a particular event to each receiver.
Sender -> Message -> Message Channel -> Multiple same Messages out -> to repsective Reciver
Point-to-Point
How can the caller be sure that exactly one receiver will receive the document or perform the call?
Send the message on a Point-to-Point Channel, which ensures that only one receiver will receive a particular message.
Sender -> Message n -> Message Channel -> Message n -> Reciver
Event-Driven Messaging
How can an application automatically consume messages as they become available?
The application should use an Event-Driven Consumer, one that is automatically handed messages as they’re delivered on the channel.
Sender -> Message -> > Event-Driven Consummer (in Reciver) -> Message to Reciver
What is middleware and which concepts exist?
Middleware is software that facilitates communication between applications.
ORB (Object Request Broker) – Facilitates communication between clients and server objects.
MOM (Message-Oriented Middleware) – Supports asynchronous messaging.
ESB (Enterprise Service Bus) – A central integration platform.
What are the DW, DF, and DR solutions for data integration
DW (Data Warehouse): Stores structured data for analytics, in a single database.
DF (Data Federation): Provides real-time access across multiple sources.
DR (Data Replication): Copies and synchronizes data between systems for consistency.
Three core integration approaches
Information-oriented (data) – Integration based on data sharing.
Service-oriented (functionality) – Integration based on services and APIs.
Process-oriented (behavior) – Integration of business processes.
What is metadata?
Metadata describes data, such as:
Protocols
Timestamps
Error codes
Authentication
Two Similarities Between Common Database and File-Oriented System Integration
Data Sharing – Both methods involve storing data in a central location that different systems can access.
Batch Processing – Both approaches often work in non-real-time mode, where data is written and later read by another system.
Two Differences Between Message- and RPC-Oriented System Integration
Communication Type:
Message-Oriented Middleware (MOM) supports asynchronous communication.
Remote Procedure Call (RPC) requires synchronous communication.
Decoupling:
MOM allows for loose coupling, meaning the sender and receiver do not need to be active simultaneously.
RPC requires tight coupling, as both systems need to be available at the same time.
Similarity Between REST and Web Services
Both provide a way to allow communication between distributed systems over a network using standard web protocols.
Main Advantage of High Coupling Between Integrated Systems
Efficiency and Performance: High coupling can lead to faster interactions since systems are more tightly integrated and can exchange data with minimal overhead.
Main Advantage of Low Coupling Between Integrated Systems
Flexibility and Scalability: Systems can evolve independently, making it easier to replace or update components without affecting the whole system.
Are Common Database and File-Oriented Systems High or Low Coupling?
Common Database: Tightly coupled – All applications depend on the shared database, requiring consistent schema and performance.
File-Oriented: Loosely coupled – Files are exchanged asynchronously, allowing each system to function independently.
Which is the main similarity, and which are 2 differences between MOM and ESB integration logics?
Similarity - Both enable asynchronous communication between systems.
Difference 1 - MOM focuses on message queuing for loose coupling. ESB offers additional features like routing, transformation, and security.
Difference 2 - MOM is best for event-driven architectures. ESB supports a broader range of integrations, including SOAP and REST APIs.
Which is the main similarity, and which are 2 differences between MOM and ORB integration logics?
Similarity - Both facilitate communication between distributed components
Difference 1 - MOM is message-based and asynchronous. ORB follows an object-based request/response model (often synchronous).
Difference 2 - MOM supports heterogeneous environments. ORB typically requires a common object model like CORBA.
Which is the main similarity, and which are 2 differences between ORB and ESB integration logics?
Similarity - Both help integrate distributed applications and services.
Difference 1 - ORB is focused on direct method calls between objects. ESB supports multiple integration methods (messaging, routing, service orchestration).
Difference 2 - ORB is typically synchronous. ESB can handle both synchronous and asynchronous communication
Orchestration vs. Choreography
Orchestration – A central controller manages service interactions (e.g., BPM engines).
Choreography – Services interact based on predefined rules without a central coordinator (e.g., event-driven systems).
Synchronous vs. Asynchronous Communication
Synchronous: The sender waits for a response (e.g., calling a web API and waiting for a response).
Asynchronous: The sender continues execution without waiting (e.g., sending an email and processing continues).
