System Integration - Midterm

SYSTEM INTEGRATION & ARCHITECTURE

The process of combining all virtual and physical components into a single cohesive infrastracture to ensure thata all an organization’s parts function as a whole.

software integration and information technology integration

System integration is also known as ___________________.

System integration

The purpose of ____ ____ is to streamline and facilitate communication not only between an organization’s internal systems but also with its external partners. System integration expedites the flow of information and reduces operational expenses.

System Integration

Expedites the flow of information and reduces operational expenses.

Integration of Legacy System Technology

This method enables the modernization of legacy systems by facilitating a seamless communication channel with more recent technological solutions and information systems.

Enterprise Application Integration (EAI)

Involves connecting and enabling communication between different software applications within an organization to ensure seamless data exchange and business process automation.

Data Integration

Enables you to connect data from various services, aggregate and transform it, and make it accessible from a central location to facilitate interactive reporting.

Enterprise-to-Enterprise integration

B2B integration is the is the automation of interorganizational business communication and processes. It enables these businesses to trade and work more efficiently with their business partners, suppliers and customers.

B2B integration

_ ______ is the is the automation of interorganizational business communication and processes. It enables these businesses to trade and work more efficiently with their business partners, suppliers and customers.

Electronic Document Exchange

The exchange of standardized business documents between companies.

1. Integration of Legacy System Technology

2. Enterprise Application Integration (EAI)

3. Data Integration

4. Enterprise-to-Enterprise integration

5. Electronic Document Exchange

(5) System Integration Types

Point-to-point Integration

Refers to direct, one-to-one communication between two systems or applications, where each system communicates with the other directly without an intermediary or centralized hub.

Star Integration

Also known as spaghetti method, connects each subsystem to other subsystem using point-to-point connection.

Hub-and-spoke Integration

A central hub acts as the central point of coordination, while each subsystem (referred to as a spoke) connects only to the hub, not directly to other subsystems.

Vertical Integration

Various systems are linked by constructing a functional “silo” that begins with the most fundamental function at the bottom and becomes progressively more complex as it ascends. It is ideal for developing basic, singlefunction integrations.

Horizontal Integration

It facilitates communication between subsystems. It is achieved using a single specialized subsystem known as an Enterprise Service Bus (ESB) that connects all other subsystems via a common user interface layer

Enterprise Service Bus (ESB)

Horizontal Integration facilitates communication between subsystems. It is achieved using a single specialized subsystem known as an _____ that connects all other subsystems via a common user interface layer

1. Point-to-point Integration

2. Star Integration

3. Hub-and-spoke Integration

4. Vertical Integration

5. Horizontal Integration

(5) System Integration Methods

1. Determine requirements

2. Analyzed feasibility

3. Architect design

4. Develop the management plan

5. System integration design

6. Implementation

7. Maintenance

(7) STAGES IN SYSTEM INTEGRATION

legacy, monolithic

CHALLENGES OF SYSTEM INTEGRATION

Organization operating on _____, _____ systems may face difficulties with integration

system integration tools

CHALLENGES OF SYSTEM INTEGRATION

Given the variety of ____ _____ _____ in the market, it can be difficult to select the one that best meets your specific business needs

Kaseya

Today, ____ is a leader in IT and security management software, with a suite of products that includes solutions for remote monitoring and management, security, backup and recovery, and more.

1. VSA (remote monitoring and management)

2. IT Glue (IT documentation)

Deep workflow integration between application such as 1.)________ , and 2.)______ not only simplify IT management but also save technicians a ton of time they would spend switching between multiple disparate applications.

Efficient Workflow

By connecting systems and eradicating manual processes, integration and architecture enable organizations to streamline their workflow. It enables the automated flow of information, reduces duplication of efforts, and increases overall operational efficiency

• Ex.: Customer relationship management

Data Accuracy and Consistency

Ensures that data across multiple systems are consistent and accurate. Organization can eliminate data silos, reduce data duplication, and ensure that all relevant systems and users have access to current and accurate information. -

• Ex.: Educational institutions: Student Information and Learning Management system

Enhanced Decision-Making

Provides organization with a comprehensive view of their data and system, enabling them to make more informed decisions.

- Ex.: Integration of sales from various channels

Scalability and Flexibility

Designing systems that are modular and loosely coupled, organization can easily add or remove components, integrate new systems or scale operations in response to changing business requirements

Improved Customer Experience

Business can provide personalized, timely, and consistent experiences across multiple touchpoints

- Ex.: Customer reservation system, loyalty program and customer service platform

Loose Coupling

Refers to designing systems with minimal interdependencies between subsystems or components. It enables the adaptability and independent evolution of integrated system, making it simple to modify, replace or add new components without affecting the entire system

Service-Oriented Architecture

An architectural methodology that prioritizes the utilization of services to facilitate system integration. Services are autonomous, loosely coupled components with well-defined interfaces for leveraging their capabilities. SOA promotes reusability, interoperability, and modularity, which makes it simpler to integrate and compose systems form diverse services.

Data Integration and Transformation

A unified view can be achieved through the process of data integration, which involves merging and consolidating data from a variety of sources. The process and transforming and mapping data from one format to another, hence maintaining compatibility and consistency across all connected systems, is referred to as data transformation.

Scalability and Performance

Refers to the capacity to manage increasing data volumes, user traffic, and transaction loads, whereas performance centers on the ability to fulfill reauction time and throughput requirements

Security and Governance

It is imperative that appropriate authentication, authorization, data protection and access control procedures be put into place to guarantee the availability, confidentiality and integrity of data.

1. Loose Coupling

2. Service-Oriented Architecture

3. Data Integration and Transformation

4. Scalability and Performance

5. Security and Governance

KEY PRINCIPLES & CONCEPTS OF SIA (5)

Migration

The transfer of data in one direction, from one system to another in a single discrete session. Components that make up migration is the source system, a set of transformation and target system.

Ex.: Moving customer data from an old CRM system to a new CRM system in one transfer.

Broadcasting

It is a process that moves data in a single direction, it is a transactional operation, it only processes data that has arrived since the last time it was transferred. The transmission of data in a manner that is either real-time or very close to real time from a single source to multiple destinations. - Ex.: Sending stock price updates from a stock exchange to multiple trading platforms.

Synchronization in Both Directions

The combining of two datasets originating from distinct systems such that each can function independently while still surviving as its own dataset (bidirectional sync) - Ex.: Syncing employee information between HR and payroll systems, allowing updates in both

Correlation

An operation similar to bi-directional sync, except it is only carried out on data that is pertinent to both systems. It filters out unnecessary information from the union process. - Ex.: Syncing inventory levels between store from systems, focusing only on stocks

Aggregation

The process of combining data from a number of different systems into a single target system, ensures that data does not get duplicated while also providing a consolidated view of realtime data that comes from multiple platforms.

Ex.: Collecting sales data from different regional offices into a central analytics system

1. Migration

2. Broadcasting

3. Synchronization in Both Directions

4. Correlation

5. Aggregation

Primary Patterns for Data Integration (5)

POINT-TO-POINT INTEGRATION

Also known as a pattern in which individual systems are connected directly to one another on a one-toone basis, it is a straightforward way for the integration of several computer systems

Direct Integration

Key Characteristics (POINT-TO-POINT INTEGRATION)

Connect two systems directly without intermediate layers or additional components

Tight Coupling

Key Characteristics (POINT-TO-POINT INTEGRATION)

System are closely linked, changes in one system may require changes in the other

Custom Interfaces

Key Characteristics (POINT-TO-POINT INTEGRATION)

Custom-built interfaces are created to enable communication between systems

Simplicity

Key Characteristics (POINT-TO-POINT INTEGRATION)

Used for smaller or less complex integrations

1. Direct Integration

2. Tight Coupling

3. Custom Interfaces

4. Simplicity

(4) Key Characteristics (POINT-TO-POINT INTEGRATION)

HUB-AND-SPOKE INTEGRATION

A pattern in which each system establishes a connection with the hub, which plays the role of a go-between and simplifies the process of exchanging data and messages among all of the system.

Centralized Hub

Key Characteristics (HUB-AND-SPOKE INTEGRATION)

It facilitates communication between multiple systems

Decoupling

Key Characteristics (HUB-AND-SPOKE INTEGRATION)

Reducing the dependency and impact of changes in one system on others

Scalability

Key Characteristics (HUB-AND-SPOKE INTEGRATION)

Easier to scale by adding new system without modifying existing connections.

1. Centralized Hub

2. Indirect Communicating

3. Decoupling

4. Scalability

(4) Key Characteristics (HUB-AND-SPOKE INTEGRATION)

PUBLISH-SUBSCRIBE INTEGRATION

A messaging paradigm where senders of messages (publishers) do not send their messages directly to specific receivers (subscribers). Instead, messages are published to a central broker, which then distributes them to all subscribers who have expressed interest in receiving messages of that type. This allows for asynchronous communication, scalability, and a decoupling of the systems involved. (Ex.: A weather application)

1. publishers

2. subscribers

PUBLISH-SUBSCRIBE INTEGRATION is a messaging paradigm where senders of messages (______) do not send their messages directly to specific receivers (subscribers). Instead, messages are published to a central broker, which then distributes them to all subscribers who have expressed interest in receiving messages of that type. This allows for asynchronous communication, scalability, and a decoupling of the systems involved. (Ex.: A weather application)

central broker

PUBLISH-SUBSCRIBE INTEGRATION is a messaging paradigm where senders of messages (publishers) do not send their messages directly to specific receivers (subscribers). Instead, messages are published to a ___ ___, which then distributes them to all subscribers who have expressed interest in receiving messages of that type. This allows for asynchronous communication, scalability, and a decoupling of the systems involved. (Ex.: A weather application)

Message Broker

Key Characteristics (PUBLISH-SUBSCRIBE INTEGRATION)

A central entity that handles the distribution of messages

(Sahana Alerting and Messaging Broker)

Topics or Channel

Key Characteristics (PUBLISH-SUBSCRIBE INTEGRATION)

Publisher send messages and from which subscriber have the ability to receives them

Asynchronous Communication

Key Characteristics (PUBLISH-SUBSCRIBE INTEGRATION)

Communication that happen independently

Scalability

Key Characteristics (PUBLISH-SUBSCRIBE INTEGRATION)

Ability to add new publisher/subscribers

1. Message Broker

2. Topics or Channel

3. Asynchronous Communication

4. Scalability

(4) Key Characteristics (PUBLISH-SUBSCRIBE INTEGRATION)

REQUEST-RESPONSE INTEGRATION

Communication pattern where one system (the requester) sends a request to another system (the responder) and waits for a response. This pattern is commonly used in web services, APIs, and other scenarios where synchronous communication is required.

1. the requester

2. the responder

Communication pattern where one system (______) sends a request to another system (_____) and waits for a response. This pattern is commonly used in web services, APIs, and other scenarios where synchronous communication is required.

Synchronous

Key Characteristics (REQUEST-RESPONSE INTEGRATION)

Requester sends a request and awaits for the responder to reply

Direct point-to-point

Key Characteristics (REQUEST-RESPONSE INTEGRATION)

System are closely linked, requester depends on the responder’s availability

Blocking

Key Characteristics (REQUEST-RESPONSE INTEGRATION)

System are closely linked, requester depends on the responder’s availability

Response

Key Characteristics (REQUEST-RESPONSE INTEGRATION)

Rely on specific protocols like HTTP, REST or SOAP

1. File-exchange

2. Asynchronous Communication

3. File Formats

4. Data Transformation

(4) Key Characteristics - REQUEST-RESPONSE INTEGRATION

FILE-BASED INTEGRATION

A method where data is transferred between systems using files. Systems generate, transfer, and consume files to share data. This pattern is often used for batch processing, large data transfers, or when systems cannot communicate directly in real time.

File-exchange

Key Characteristics (FILE-BASED INTEGRATION)

Data is exchanged between systems through file transfer

Asynchronous Communication

Key Characteristics (FILE-BASED INTEGRATION)

System does not need to be connected

File Formats

(Key Characteristics - FILE-BASED INTEGRATION)

CVS, XML or JSON

Data Transformation

Key Characteristics - FILE-BASED INTEGRATION

Data needs to be transformed to match the schema or requirement of the target system before being imported

1. File-exchange

2. Asynchronous Communication

3. File Formats

4. Data Transformation

(4) Key Characteristics - FILE-BASED INTEGRATION

REAL-TIME INTEGRATION

Real-time integration is a pattern where data is exchanged between systems with minimal delay, allowing for immediate processing and response. This approach is commonly used in scenarios where timely information is crucial, such as financial transactions, monitoring systems, and live updates.

1. Immediate Data Exchange

2. Event-driven

3. Continuous Data Flow

4. High Throughput and Low Latency

(4) Key Characteristics (REAL-TIME INTEGRATION)

Immediate Data Exchange

Key Characteristics (REAL-TIME INTEGRATION)

Data is exchanged between systems almost instantly

Event-driven

Key Characteristics (REAL-TIME INTEGRATION)

Based on events, where specific actions trigger data exchange or processing

Continuous Data Flow

Key Characteristics (REAL-TIME INTEGRATION)

Data is continuously streamed between system rather than being processed in discrete batches

High Throughput and Low Latency

Key Characteristics (REAL-TIME INTEGRATION)

Integration handles high volumes of data with minimal delay

HYBRID INTEGRATION

_______ combines multiple integration patterns and approaches to create a flexible, robust solution that meets diverse system requirements. This strategy leverages the strengths of various integration techniques (like real-time, file-based, and messaging) to address the unique needs of complex integration scenarios.

Data integration

_____ is the process of combining data from multiple sources to provide a unified view.

- It ensures consistency and completeness in data management

Data synchronization

is the process of ensuring that data across multiple systems or locations is updated and consistent in real-time or scheduled intervals.avoids discrepancies and ensures data accuracy

Synchronization

_______ avoids discrepancies and ensures data accuracy

One-Way Synchronization

Data flows from one source to another without feedback

Two-Way Synchronization

Changes made in both systems are updated bidirectionally

Real-Time Sync

Data is updated immediately (e.g., Google Docs auto-save)

Batch Sync

Data is updated periodically (e.g., payroll systems)

Data integration

refers to the process of merging two or more pieces of software so that they function in conjunction with one another

Synchronization

has the ability to maintain constant communication between databases (remain consistent with one another).

data synchronization

Thus, ____ is a subset of data integration, however, not all integration methods lead to a data set that is perfect sync with itself.

Keeping Data Secure

Data is an asset. Data can be protected from corruption and kept in a more secure state if proper data synchronization techniques are followed.

Maintaining Data Quality

Ensures that business always has access to the most accurate information possible

Quality Data Management

High quality data requires a solid basis in order to achieve consistency. When it comes to making important choices, having your data synchronized instills confidence in those choices

Data Harmonization

The process of creating a unified set of data from several data types, fields and formats

1. Keeping Data Secure

2. Maintaining Data Quality

3. Quality Data Management

4. Data Harmonization

(4) NECESSITY OF DATA SYNCHRONIZATION

Make use of integration that are built-in

Native integration occurs when two applications that you are already utilizing can be immediately integrated with one another. API’s (Application Programming Interfaces) are typically used for this purpose.

Native integration

______ occurs when two applications that you are already utilizing can be immediately integrated with one another. API’s (Application Programming Interfaces) are typically used for this purpose.

Make use of tailored integrations

Integration made to order are pieces