SIA MIDTERM REVIEWER PDF

George pogi Introduction to System Integration and Architectural Patterns System Integration – is the process of bringing together multiple subsystems into a single, unified system. APPROACHES: Point-to-Point – direct connection between systems. Pros: Simple to set up Cons: Hard to...

George pogi Introduction to System Integration and Architectural Patterns System Integration – is the process of bringing together multiple subsystems into a single, unified system. APPROACHES: Point-to-Point – direct connection between systems. Pros: Simple to set up Cons: Hard to manage as the system grows (spaghetti architecture). Hub-and-Spoke Integration – central hub controlling communication between systems. Pros: Easier to manage than point-to-point Cons: The hub becomes a single point of failure. Enterprise Service Bus (ESB) – middleware that facilitates communication. Pros: Scalable, easier to manage large systems. Cons: Requires more initial setup and can introduce complexity. ARCHITECTURAL PATTERNS IN SYSTEM INTEGRATION: Layered Architecture – Organizes software into layers (e.g., presentation, business, logic, data). When to use: Modular applications where changes to one layer do not impact others. Microservices Architecture – Breaking down a large application into small, independent services. When to use: For complex, distributed systems that need scalability. Services-Oriented Architecture (SOA) – Systems expose services to each other through network. When to use: Large organizations with many different departments needing shared devices. Event-Driven Architecture – Systems communicate by generating and reacting to events. When to use: Real-time systems like trading platforms or social media notifications. Publish-Subscribe Architecture – Publishers send message without knowing who subscribes to them. When to use: Asynchronous communication where the sender and receiver don’t need to interact in real-time. Examples: Amazon (Microservices) Netflix (Event-Driven Architecture) Banking Systems (SOA) 1 George pogi AMAZON AND MICROSERVICES ARCHITECTURE: Decoupling of Services – Amazon’s systems is divided into small, autonomous services, each responsible for a specific functionality (e.g., search, payments, product catalog, recommendations). Each microsercives operates independently and communicates with other services through APIs. Scalability – If Amazon’s search function experiences heavy traffic (e.g., during Black Friday), only the search microservices is scaled up, without impacting other services like payments or user accounts. Faster Development and Development – Different teams can work on different services without waiting for others to complete their work. This enables Amazon rapidly develop and deploy new features. Failure Isolation – If one services (e.g., recommendations) fails, it doesn’t bring down the entire system. Other services like payments and product listing can continue functioning. BANKING SYSTEM AND SERVICES ORIENTED ARCHITECTURE (SOA): Credit Checks – When a customer applies for a loan or credit card, a credit check service communicates with external agencies to assess the customer’s creditworthiness. Account Management – The account management service handles personal information, and managing savings or checking accounts. Payment Processing – The payment processing service deals with transaction requests, whether for bill payments, online purchases, or fund transfers. API using POSTMAN: GET – Retrieve data POST – Create new resources PUT – Update or create resources PATCH – Partially update resources DELETE – Remove resources OPTIONS – Query allowed methods HEAD – Retrieve headers only TRACE – Message loop-back test CONNECT – Establish a tunnel 200 Ok - for successful data retrieval 201 Created - for successful resource creation. 400 Bad Request - for invalid input data. 401 Unauthorized - when authentication is required but not provided 500 Internal Service Error - to identify server-side issues. 2 George pogi Middleware Solutions in System Integration IMPORTANCE OF MIDDLEWARE: Middleware – specialized software that connects different systems, applications, or services within a computing environment, enabling them to communicate and exchange data efficiently. It acts as an intermediary, allowing systems that may be built on different platforms, languages, or databases to interact smoothly. System integration – is about creating a seamless flow of information between different systems to improve business processes. Middleware plays a critical role in this by facilitating communication between these systems without the need for each to be modified extensively. Interoperability – Middleware enables systems built using different technologies to work together. For example, middleware can allow an older legacy system to integrate with modern applications. Scalability – Middleware can manage high volumes of communication and data transfer, ensuring that systems can grow without performance degradation. Security – Middleware often includes mechanism for secure communication, encryption, and authentication, providing a reliable platform for data. Error Handling and Monitoring - Middleware can manage faults, retries, and delays in communication, ensuring reliability in system integration. COMPONENTS OF MIDDLEWARE: Message-Oriented Middleware (MOM) – this type of middleware facilities communication between applications through messages. It ensures that data flows smoothly between systems, even if one is temporarily unavailable. Example include RabbitMQ or ActiveMQ.. Database Middleware – middleware that provides communication between applications and databases. This allows multiple applications to access and modify data within a centralized or distributed database. Transaction Middleware – This ensures that all operation across distributed systems are completed successfully, making it essential for business applications that involve complex transactions (e.g., financial systems). Application Servers – Middleware like JBoss or WebSphere provides an environment where application can run, handling the communication between the apps and underlying systems. 3 George pogi Enterprise Service Bus (ESB) is a vital middleware component in large-scale system integrations. It serves as a hub through which different systems communicate via common bus architecture. The ESB routes, transforms, and translates messages between various applications, ensuring that all systems involved can interact without needing direct connections to each other. An example of an ESB is MuleSoft or IBM WebSphere. Cloud-based middleware, known as Integration Platform as a Service (iPaaS), allows organizations to integrate their cloud and on-premise systems seamlessly. These platforms provide pre-built connectors, tools, and services to facilitate the rapid development of integrations. Example include Dell Boomi and Microsoft Azure Integration Services. MIDDLEWARE PROTOCOLS: SOAP (Simple Object Access Protocol) – a protocol used for exchanging structured information in the implementation of web services. It is secure and often used in enterprise-level applications. REST (Representational State Transfer) – is an architectural style that uses HTTP requests for communication. It is more lightweight and often used for public APIs and web-based applications. GRPC (Google Remote Procedure Call) – a high-performance open-source RPC framework designed for efficient communication between microservices. MIDDLEWARE USE CASES: Legacy System Integration – Middleware allows organizations to integrate old systems with modern applications, extending their lifespan and usability. Microservices Architecture – In microservices, middleware components like message brokers or API gateways help services communicate in a decoupled manner, ensuring flexibility and scalability. Hybrid Cloud Integration - Middleware helps organizations connect on-premise system with cloud platforms, facilitating hybrid cloud strategies. MIDDLEWARE SOLUTIONS: Apache Kafka – A distributed messaging platform that is ideal for real-time streaming and data integration. IBM MQ – An enterprise messaging system for secure and reliable data transmission. TIBCO – Provides middleware solutions for business process integration and complex event processing. 4 George pogi Data Management in System Integration INTRODUCTION TO DATA MANAGEMENT IN SYSTEM INTEGRATION In system integration, data management refers to the process, practices, and tools used to ensure that data flows smoothly between different systems, maintaining accuracy, consistency, and security. When organization integrate multiple systems-like an e-commerce platform with a customer relationship management (CRM) system-proper data management ensures that information, such as customers details or orders, is synchronized correctly across these systems. IMPORTANCE OF DATA MANAGEMENT IN INTEGRATION:  Without effective data management, systems may end up with inconsistent data (e.g., different versions of customer addresses in different systems), leading to errors.  Proper data management ensures data can be shared, used and trusted across various systems without duplication or confusion. COMMON DATA MANAGEMENT STRATEGIES IN INTEGRATION: ETL (Extract, Transform, Load) – Involves extracting data from one system, transforming it to a format that fits the target system, and loading it into that system. Data Replication – This is when data is copied from one database to another to ensure that both systems have identical information. Data Federation – Data is accessed in real-time from multiple systems without moving or copying it. This gives the appearance of unified system without centralizing the data. CHALLENGES OF DATA MANAGEMENT IN SYSTEM INTEGRATION: Data Silos – When different departments or systems store data separately, this leads to silos, where data isn’t shared or connected. Integration efforts aim to break down these silos. Data Inconsistency – When data formats or structures differ between systems, it’s hard to ensure that data remains accurate as it moves between them. Data Security and Privacy – Moving data between systems poses security risks, especially if the data is sensitive (like customer information). It’s important to use encryption and ensure compliance with regulations (e.g., GDPR). 5 George pogi Data Quality – Ensuring the data is clean and accurate before integrating is key. Poor data quality in one system can lead to errors across all integrated systems. TOOLS AND TECHNOLOGIES FOR DATA MANAGEMENT IN SYSTEM INTEGRATION: Middleware Solutions – Middleware acts as a bridge between different systems, helping them communicate and exchange data. Examples include Apache Camel, MuleSoft and Dell Boomi. Database Management Systems (DBMS) – These manage how data is stored and retrieved in integrated systems. Common DBMS tools include MySQL, Oracle, and PostgreSQL. Data Governance Tools – Tools like Talend and Informatica ensure data quality, security and compliance as it moves between systems, helping organizations establish rules for managing and using data. 6 George pogi 7