SIA345

Layered Architecture

Divides the system into logical layers, each responsible for specific functionalities.

Layered Architecture

Layers are organized hierarchically, with higher layers depending on lower layers.

Layered Architecture

Common layers include presentation/UI, business logic, and data access layers.

Layered Architecture

Promotes separation of concerns and modularity.

Microservices Architecture

An architectural development style where the application is composed of smaller services that handle a portion of functionality and communicate via lightweight protocols like HTTP.

Microservices Architecture

Relatively easier to manage due to smaller size.

Microservices Architecture

Updating one service requires redeploying only that specific service.

Microservices Architecture

Self-contained and deployed independently with shorter start-up and deployment times.

Microservices Architecture

Allows new developers to understand only the service they work on instead of the entire system.

Microservices Architecture

Enables horizontal scaling by scaling only the overloaded service.

Microservices Architecture

Each service can use different technology depending on business needs.

Microservices Architecture

A service failure doesn't impact others, keeping the rest of the system operational.

Microservices Architecture

More complex than monolithic applications due to distributed nature.

Microservices Architecture

Complexity increases with the number of individual services.

Microservices Architecture

Requires skilled developers to identify and manage inter-service communication.

Microservices Architecture

Independent deployment is more complicated.

Microservices Architecture

Higher network cost due to inter-service communication causing latency.

Microservices Architecture

Less secure due to communication over the network.

Microservices Architecture

Debugging is harder because control spans multiple services.

Monolithic Architecture

All functionalities are contained within a single codebase.

Event-driven Architecture

Relies on the capture, communication, processing, and persistence of events.

Event-driven Architecture

Enables minimal coupling and is ideal for distributed applications.

Event-driven Architecture

Loosely coupled since producers are unaware of consumers and consequences.

Event

A significant occurrence or change in state in hardware or software.

Event

Not the same as a notification, which informs a part of the system that an event occurred.

Event

Can originate from internal or external inputs.

Event

Can be triggered by user actions, external sources, or system operations.

Apache Kafka

A distributed platform widely used for real-time event processing.

Apache Kafka

Handles publishing, subscribing, storing, and processing of event streams.

Apache Kafka

Supports high-throughput, scalable applications by reducing point-to-point integrations.

Event-driven Architecture Models

May use either a pub/sub or an event stream model.

Pub/Sub model

This is a messaging infrastructure based on subscriptions to an event stream.

Pub/Sub model

With this model, after an event occurs, or is published, it is sent to subscribers that need to be informed.

Event Streaming model

events are written to a log.

Event consumers don’t subscribe to an event stream.

Event Streaming model

they can read from any

part of the stream and can join the stream at any time.

Service-Oriented Architecture (SOA)

Organizes software as a set of services that communicate with each other.

Service-Oriented Architecture (SOA)

An enterprise-wide method using reusable software components or services.

Service-Oriented Architecture (SOA)

A service includes code and integrations for a specific business function.

Service-Oriented Architecture (SOA)

Services are self-contained, loosely coupled, and focused on specific functionality.

Service-Oriented Architecture (SOA)

Exposes well-defined interfaces and can be reused across platforms.

Service-Oriented Architecture (SOA)

Encourages interoperability, modularity, and flexibility in design.

Difference between Microservices vs. Service-Oriented Architecture (SOA)

SOA has enterprise scope, while the other has application scope.

Integration Techniques and Patterns

Approaches to connect various systems or components for seamless operation.

Integration Techniques and Patterns

Enables data exchange, communication, and coordination across systems.

Data Integration

Combines data from multiple sources to provide a unified view.

Data Integration

Approaches depend on data complexity, volume, real-time needs, and integration goals.

Application Integration

Connects and allows communication between different applications or components.

Application Integration

Uses different methods depending on architecture and technology involved.

Orchestration

A centralized method for integrating services.

Orchestration

Uses a central engine to coordinate interactions between services.

Orchestration

Defines the order and flow of data among services in a business process.

Orchestration

Directs and controls execution of services in a coordinated manner.

Orchestration

Specifies timing and invocation details for each service.

Orchestration

Enforces communication interfaces between services.

Orchestration

Uses request-response communication and often waits for service replies.

Choreography

A decentralized approach to integrating services.

Choreography

Services communicate based on predefined message formats or contracts.

Choreography

Each service understands its responsibilities and interaction methods.

Choreography

No central coordinator; interaction is contract-driven.

Choreography

Services are aware of their roles and act accordingly.

Choreography

Uses asynchronous messaging without waiting for replies.

Choreography

Loosely coupled; changes in one service don't affect others.

Choreography

Uses events or messages to trigger workflows across services.

Integration Middleware and Tools

Helps manage and facilitate integration across systems and data.

Integration Middleware and Tools

Provides capabilities to connect, transform, route, and monitor interactions.

Integration Governance

A set of policies and practices to oversee system and data integration.

Integration Governance

Ensures effective and efficient collaboration between different technology components.

Standards and Guidelines

Defines integration practices and consistency across teams.

Standards and Guidelines

Helps maintain best practices in implementations.

Architecture and Design

Describes integration infrastructure including APIs and middleware.

Architecture and Design

Simplifies system integration and avoids data silos.

Data Management

Ensures data quality, security, and compliance across systems.

Security and Compliance

Protects data and enforces access control.

Security and Compliance

Ensures adherence to regulatory and industry requirements.

Monitoring and Performance Management

Keeps track of integration processes to detect issues.

Monitoring and Performance Management

Tracks performance to meet service level expectations.

Change Management

Controls updates to integration parts to avoid service disruption.

Vendor Management

Ensures vendors follow standards and are held accountable.

Governance Board

Oversees integration decisions and resolves conflicts in projects.

System Integration Governance Frameworks

Helps manage application and system integrations efficiently and securely.

System Integration Governance Frameworks

Provides policies and processes for controlling integration.

TOGAF (The Open Group Architecture Framework)

Provides a method to plan, design, and govern enterprise architectures.

TOGAF (The Open Group Architecture Framework)

Used to set integration standards and governance policies.

COBIT (Control Objectives for Information and Related Technologies)

A framework for managing IT governance and practices.

COBIT (Control Objectives for Information and Related Technologies)

Defines integration policies aligned with business and compliance goals.

ITIL (Information Technology Infrastructure Library)

A set of ITSM practices aligned with business needs.

ITIL (Information Technology Infrastructure Library)

Manages integration as part of incident, change, and service level management.

API Governance Frameworks

Focuses on API security, lifecycle, versioning, and monitoring.

Integration Best Practices

Guidelines for effective and seamless system or data integration.

Integration Best Practices

Proper implementation improves processes and productivity.

Identity and Access Management (IAM)

Manages digital identities and their access to IT resources.

Identity and Access Management (IAM)

Ensures right access for the right users based on roles and needs.

Protocol

A set of rules for communication between systems or entities.

Protocol

Defines message formats, semantics, and order for interaction.

Protocol

Enables reliable and secure communication between devices and applications.

Protocol

Standardizes cross-system collaboration regardless of vendor.

Secure Communication Protocols

Cryptographic protocols ensuring confidentiality and integrity of transmitted data.

Secure Communication Protocols

Protects sensitive data from unauthorized access and tampering.

Threat Modeling

A method to identify, evaluate, and reduce system vulnerabilities.

Threat Modeling

Used in designing secure applications and systems.