COURSE MODULE: SYSTEMS INTEGRATION, MIDDLEWARE, ERP,
INTEGRATION PATTERNS
LESSON 1: Systems Integration Approach and Its Applications
Learning Objectives
Students will be able to:
Define systems integration
Explain its importance
Identify real-world applications
Systems Integration is the process of linking different IT systems so they function as one
unified system.
Why Systems Integration is Important
Eliminates data redundancy
Improves efficiency
Enables automation
Supports decision-making
Systems Integration Approaches refer to the different ways or strategies used to connect
multiple systems, applications, or components so they can work together as a unified system.
Think of it as:
“How systems are connected and communicate with each other.”
MAIN SYSTEMS INTEGRATION APPROACHES
1. Point-to-Point (P2P) Integration
Each system is directly connected to another system.
Example
Enrollment system directly connects to payment system
Payment system directly connects to reporting system
Advantages
Simple to implement (for small systems)
Fast communication
Disadvantages
Becomes very complex as systems grow
Hard to maintain (“spaghetti architecture”)
2. Vertical Integration (Silo Approach)
Systems are integrated based on specific functions or departments
Example
HR system integrates only HR-related tools
Finance system integrates only accounting tools
Advantages
Simple and fast within a department
Lower initial cost
Disadvantages
Creates data silos
Poor cross-department communication
3. Star Integration (Spaghetti Integration)
A variation of P2P where multiple systems are interconnected in many directions
Example
Every system connects to every other system
Disadvantages
Extremely complex
Difficult to troubleshoot
4. Horizontal Integration (Enterprise Service Bus – ESB)
Uses a central communication layer (bus) to connect systems
Example
Systems communicate through a shared middleware layer
Advantages
Scalable
Flexible
Easier to manage
Disadvantages
Requires expertise
Higher setup complexity
5. API-Based Integration
Systems communicate using Application Programming Interfaces (APIs)
Example
Mobile app retrieves data via REST API
Advantages
Modern and widely used
Flexible and reusable
Disadvantages
Requires API management and security
6. Event-Driven Integration
Systems communicate by triggering and responding to events
Example
“Order placed” → triggers inventory update and notification
Advantages
Real-time processing
Highly scalable
Disadvantages
Harder to monitor and debug
COMPARISON SUMMARY
Approach Best For Key Issue
P2P Small systems Not scalable
Vertical Departmental systems Data silos
Star Simple setups Complexity explosion
Horizontal (ESB) Enterprise systems Setup complexity
API-Based Web/mobile apps Security management
Event-Driven Real-time systems Debugging difficulty
SIMPLE WAY TO UNDERSTAND IT:
P2P → “Everyone talks directly”
Vertical → “Each department works alone”
Star → “Too many connections = messy”
ESB → “Everyone talks through a central highway”
API → “Systems request services from each other”
Event-driven → “Systems react automatically to events”
Applications of Systems Integration
1. Healthcare Systems
Integration of patient records, lab results, billing
Result: Faster diagnosis, better patient care
2. E-Commerce
Payment systems + Inventory + Logistics
Result: Seamless online shopping experience
3. Banking Systems
ATM + Mobile Banking + Core Banking
Result: Real-time financial transactions
4. Education Systems
Enrollment + Grading + LMS
Result: Centralized student information
Concept Check
Question:
Why is systems integration important in large organizations?
LESSON 2: Middleware Models
Learning Objectives
Students will be able to:
Define middleware
Identify and compare middleware models
Middleware is software that acts as a bridge between applications.
Middleware Models
1. Point-to-Point (P2P)
Direct connection between systems
✔ Simple
❌ Not scalable
2. Hub-and-Spoke
Central hub manages communication
✔ Easier management
❌ Single point of failure
3. Enterprise Service Bus (ESB)
Uses a communication bus
✔ Scalable and flexible
❌ Complex
4. API-Based Middleware
Uses APIs for communication
✔ Modern and widely used
❌ Needs security and version control
5. Event-Driven Middleware
Systems react to events
✔ Real-time processing
❌ Complex debugging
Comparison Table
Model Best Use Limitation
P2P Small systems Complex scaling
Hub-Spoke Medium systems Failure risk
ESB Enterprise systems Complexity
API Web/mobile apps Security issues
Event-driven Real-time apps Debugging
Activity
Case: A growing online store
Which middleware model should be used? Why?
LESSON 3: ERP Systems and Their Processes
Learning Objectives
Students will be able to:
Define ERP
Identify ERP modules
Explain ERP processes
Enterprise Resource Planning (ERP) integrates all business processes into one system.
Examples:
SAP ERP
Oracle ERP Cloud
Core ERP Processes
1. Procurement
Request → Approval → Purchase
2. Inventory Management
Tracks stock levels in real time
3. Production Planning
Scheduling and manufacturing
4. Sales and Distribution
Order → Delivery → Billing
5. Finance and Accounting
Financial reporting
Budget tracking
ERP Workflow Example
Customer Order
⬇
Inventory Check
⬇
Production
⬇
Delivery
⬇
Billing
⬇
Financial Recording
Key Insight
ERP removes data silos and ensures data consistency
Activity
Scenario:
A company has delays in inventory updates.
Students identify:
Which ERP module is affected
How ERP solves the issue
LESSON 4: Integration Patterns and Solutions
Learning Objectives
Students will be able to:
Identify integration patterns
Apply patterns to real-world problems
What are Integration Patterns?
Reusable solutions to common integration problems.
Common Integration Patterns
1. Request–Response Pattern
A system sends a request and waits immediately for a reply before continuing.
Key Characteristics
Synchronous (blocking)
Immediate feedback required
Tight coupling between systems
When to Use
Use this when:
The user/system needs an instant answer
The process cannot continue without a response
Real-time validation is required
Applications
Login/authentication systems
Payment processing (e.g., card validation)
Searching a database (e.g., student records)
Form validation (checking username/password)
Example Flow
User → Login Request → Server → Validate → Response (Success/Fail)
If the server is slow → the user waits
2. Publish–Subscribe Pattern (Pub-Sub)
One system (publisher) sends a message, and multiple systems (subscribers) receive it
automatically.
Key Characteristics
Asynchronous
Loosely coupled
One-to-many communication
When to Use
Use this when:
Many systems need the same information
You want to decouple sender and receivers
Real-time updates to multiple users/services
Applications
Notification systems (SMS, email, app alerts)
Social media feeds (new post notifications)
Stock price updates
IoT systems (sensor broadcasts data)
Example
Teacher posts announcement → All students receive it instantly
Publisher doesn’t care who receives the message
3. Message Queue Pattern
Messages are placed in a queue (line) and processed one at a time.
Key Characteristics
Asynchronous
Reliable (messages are not lost)
Handles traffic spikes
When to Use
Use this when:
Tasks can be processed later
Systems operate at different speeds
You need fault tolerance
Applications
Order processing in e-commerce
Email sending systems
Background jobs (report generation)
Banking transactions
Example
Customer places order → queued → processed by worker system
Even if the system crashes, the message stays in the queue
4. Data Transformation Pattern
Converts data from one format to another so systems can understand each other.
Key Characteristics
Enables interoperability
Often used in middleware
Can involve mapping, filtering, restructuring
When to Use
Use this when:
Systems use different data formats
Integrating legacy systems
Data must be standardized
Applications
XML ↔ JSON conversion
Database schema mapping
Data migration projects
API integrations
Example
Old system sends XML → middleware converts → new system reads JSON
Without this, systems “can’t talk”
5. API Gateway Pattern
A single entry point that manages all client requests and routes them to the correct services.
Key Characteristics
Centralized control
Handles authentication, routing, rate limiting
Common in microservices architecture
When to Use
Use this when:
You have multiple backend services
You want to simplify client access
Security and monitoring are important
Applications
Mobile apps connecting to multiple services
Microservices-based systems
Cloud-based platforms
Enterprise systems
Example
Mobile app → API Gateway → routes to:
User service
Payment service
Notification service
Client doesn’t need to know internal system complexity
Integration Problems & Solutions
Problem Solution
Data mismatch Data Transformation
High traffic Message Queue
Tight coupling API-based integration
Real-time updates Event-driven
Complex system ESB
Activity (Application-Based)
Scenario:
A university system includes:
Enrollment
Payment
Learning Management System
Task:
Students must:
1. Identify the problem
2. Choose:
o Middleware model
o Integration pattern
3. Explain their solution
ASSESSMENT
Questions
1. Compare ESB and API-based integration.
2. Propose an integration solution for a hospital system.
3. Which integration pattern is best for real-time alerts? Explain.