1.1 Part 1: Intro to System Integration and Architecture

Prelim Topic

Systems Integration

• The process of combining various subsystems or components to work together as a unified system. This integration ensures seamless communication and data exchange between different systems, enhancing overall functionality and efficiency

Horizontal Integration

(Integration Types)

• Connects different systems or applications at the same level of the technology stack. For example, integrating various software applications that handle similar types of data or functions.

Vertical Integration

(Integration Types)

• Involves connecting systems across different levels of the technology stack, such as linking data sources with applications and user interfaces. This approach is often used to ensure end-to-end functionality.

Functional Integration

(Integration Types)

• Focuses on integrating different functionalities or modules within the same system, This type of integration is critical for creating a cohesive and well-functioning application.

Middleware

• Software that facilitates communication between different systems or applications, It acts as an intermediary, enable disparate systems to interact and share data effectively

Message Brokers

(Middleware Types)

• Facilitate message exchange between different systems

API Gateways

(Middleware Types)

• Manage and route API requests, ensuring proper communication between clients and services

Database Middleware

(Middleware Types)

• Connects applications to databases, handling data transactions and queries

Application Programming Interfaces (APIs)

• Are sets or rules and protocols that allow different software applications to communicate with each other. They define how requests and responses should be formatted, enabling integration and data exchange

• They are crucial for enabling interaction between disparate systems and services, making them a key component of modern system integration

Monolithic Architecture

(Architectural Styles)

• All components of the application are interconnected and operate as a single unit. This architecture can simplify development but may pose challenges with scalability and maintenance as the application grows.

Layered Architecture

(Architectural Styles)

• Divides the system into distinct layers (ex. presentation, business logic, data access) that interact with each other in a hierarchical manner. This separation of concerns simplifies development and maintenance

Microservices Architecture

(Architectural Styles)

• Decomposes the system into small, independent services that communicate through APIs. Each microservice handles a specific business function and can be developed, deployed, and scaled independently

Services-Oriented Architecture (SOA)

(Architectural Styles)

• Designs the system as a collection of loosely coupled services that interact through standardized protocols.

• Promotes reuse, flexibility, and ease of integration with other services

Modularity

(Design Principles)

• Breaking down the system into smaller, manageable components or modules that can be developed and maintained independently.

• Enhances flexibility and ease of maintenance

Scalability

(Design Principles)

• Designing the system to handle increased load and data volume without significant performance degradation.

• These systems can grow with increasing demands

Interoperability

(Design Principles)

• Ensures that different systems and components can work together seamlessly, even if they are built on different technologies or platforms.

• Is crucial for creatin integrated and functional systems.