SIA—MODULE 2

Web Services

Protocols facilitating communication and interoperability between software systems via a network.

Web Services

These services are delivered via the World Wide Web.

Web Services

Open standards such as XML (eXtensible Markup Language), SOAP (Simple Object Access Protocol), and HTTP (Hypertext Transfer Protocol) provide the foundation upon which web services are constructed.

XML (eXtensible Markup Language),

SOAP (Simple Object Access Protocol),

and HTTP (Hypertext Transfer Protocol)

Open standards such as _,_,_ provide the foundation upon which web services are constructed.

eXtensible Markup Language

XML

Simple Object Access Protocol

SOAP

Hypertext Transfer Protocol

HTTP

Application Programming Interfaces

APIs

SOAP-Simple Object Access Protocol

REST- Representational State Transfer

GraphQL

3 API

SOAP (Simple Object Access Protocol)

Example: A SOAP-based web service returns an XML response containing weather forecasts based on a location request.

SOAP (Simple Object Access Protocol)

A communication protocol built on XML (eXtensible Markup Language) to exchange structured data.

Communicates with a consistent structure; platform- and language-independent.

REST (Representational State Transfer)

An architectural style leveraging the HTTP protocol (GET, POST, PUT, DELETE) for web services.

REST (Representational State Transfer)

Stateless client-server communication; relies on lightweight data formats like JSON.

REST (Representational State Transfer)

Example: An e-commerce API allows clients to retrieve products, add items to a cart, and place orders using HTTP methods.

GraphQL

A query language for APIs and a runtime for executing those queries.

Gives clients the ability to request only the data they require, cutting down on over-fetching.

GraphQL

Example: A social media platform uses a GraphQL API to allow clients to request specific user profile information and posts in a single query.

Message-Oriented Middleware (MOM)

Refers to software architecture providing a message

backbone that manages reliable message delivery, routing,

and transformation.

Message-Oriented Middleware (MOM)

It ensures that messages are delivered even in the event that

neither the sender nor the receiver is available at the same

time, or if there are problems with the network or the system.

Message Queuing (MQ)

An essential service that is offered by MOM.

Message Queuing (MQ)

It entails storing messages in queues and managing those

queues until the messages are consumed by the receivers for

whom they were intended.

queue

used by the sender to store messages, and the queue is used by the receiver to retrieve and process message in an asynchronous manner.

store, retrieve and process

A queue is used by the sender to _ messages, and the

queue is used by the receiver to _ and _ message

in an asynchronous manner.

ARLF

Asynchronous Communication

Reliable Delivery

Load Balancing

Fault Tolerance

Benefits of Message Queues

Asynchronous Communication:

Enables decoupled, asynchronous system communication without waiting for an instant response.

Reliable Delivery

Messages are saved until successfully processed, assuring reliable distribution even if systems are temporarily unavailable.

Load Balancing

Tasks can be distributed over numerous consumers simultaneously, improving scalability and system performance.

Fault Tolerance

Messages are held in persistent queues and can be accessed and processed when systems recover.

EOEI

1.Enterprise Messaging (e.g., banking systems, payment

gateways, customer relationship management systems)

2.Order Processing (e.g., inventory management, shipping and

billing)

3.Event-Driven Architecture (EDA)

4.Internet of Things (IoT)

Common MOM/MQ Use Cases

Service-Oriented Architecture (SOA)

Is the form of architecture that places an emphasis on the development of services as reusable architectural components in order to facilitate interoperability and flexibility in the process of system integration.

S—RDLIC

Service Reusability

Service Discoverability

Service Loose Coupling

Service Interoperability

Service Composability

Principles of SOA

Service Reusability

Services are designed to be used in various applications to reduce code duplication.

Service Discoverability

Services are made locatable through service registers and directories.

Service Loose Coupling

Low dependency between services allows them to be independently updated and deployed.

Service Interoperability

Relies on open standards (XML, SOAP, REST) to achieve seamless communication.

Service Composability

Synthesis of different services into intricate business procedures (orchestrated or choreographed).

EBaTG

• E-Commerce Platform

• Bank System

• Travel Booking System

• Government Services

Examples of SOA

E-commerce Platform

Product catalog, inventory, payment, and order fulfillment are implemented as separate, reusable services.

Banking System

Account administration, transaction processing, and fraud monitoring are handled by SOA-powered services.

Travel Booking System

Combines services for flight/hotel bookings, vehicle rental, and payment processing into a single system to manage complex travel plans.

Government Services

Services manage social welfare programs, online tax filing, and permit granting, coordinating them for streamlined and effective public offerings.

Event-Driven Architecture (EDA)

• An architecture emphasizing the sequence of events and the responses they trigger (asynchronous, real-time processing).

• Systems are able to communicate with one another and react to events in an EDA, which enables decoupled, asynchronous, and real-time processing.

E—PCCPD

Event Producer

Event Consumer

Event Channel

Event Processing

Event-Driven middleware

Principles of EDA

Event Producers

Components that generate events (internal workings or external environment changes).

Event Consumers

Components that subscribe to events and react to them, often triggering additional processes.

Event Channels

The communication path (e.g., message queues, Pub/Sub) between producers and consumers.

Event Processing

Determining what to do based on event data, triggering relevant actions in real-time or batch-oriented fashion.

Event-Driven Middleware

The infrastructure and tools necessary to perform EDA are often provided by event-driven middleware. This middleware contains elements such as event routers, event brokers, and event processing engines, which manage event filtering, routing, and processing.

InFiLoSoDi

Internet of Things

Financial Trading Systems

Logistic and Supply Chain Management

Social media and notifications

Distributed system integration

Examples of EDA

Internet of Things (IoT)

Processing huge amounts of sensor data in real-time to trigger actions (e.g., smart home monitoring).

Financial Trading Systems

Rapidly responding to changes in market price, trade executions, or order cancellations.

Logistic and Supply Chain Management

Real-time tracking of goods, inventory levels, and vehicle locations allows systems to instantly trigger restocking orders or reroute shipments in response to delays.

Social Media and Notifications

User actions (likes, posts, comments) generate events that asynchronously update feeds, send push notifications, and trigger analytics without slowing down the user interface.

Distributed System Integration

Disparate applications (legacy, cloud, and SaaS) communicate by exchanging events rather than direct requests, enabling loose coupling and allowing new systems to be added without disrupting existing ones.

Microservices Architecture

Refers to a particular architectural style that organizes an

application as a collection of individual services that are

relatively small and independent.

Microservices Architecture

Each service is geared toward a certain business capability and

is capable of being independently developed, deployed, and

scaled.

SSLIR

Service Independence

Single Responsibility

Loose Coupling

Independent Data Management

Resilience and Fault isolation

Principles of Microservices Architecture

Service Independence

Services operate on their own without external intervention, providing flexible scaling.

Single Responsibility

Each microservice is responsible for one specific business capability.

Loose Coupling

Communication uses lightweight protocols (HTTP/REST or messaging systems).

Independent Data Management

Each service has its own database or data store, preventing a single point of failure.

Resilience and Fault Isolation

Microservices are built to handle errors without bringing down the entire system.

ERFMT

E-commerce Platform

Ride-sharing application

Financial services

Media Streaming Platform

Travel booking system

Examples of Microservices Architecture

E-commerce Platform

Management of users, product catalog, order processing, and payment are handled by separate services.

Ride-Sharing Application

Services manage user registration, trip calculation, payment, and tracking in real-time.

Financial Services

Separate, secure services handle distinct functions such as account management, transaction processing, fraud detection, and notifications.

Media Streaming Platform

Specific microservices are dedicated to user authentication, video transcoding, recommendation engines, and subscription management to handle high traffic.

Travel Booking System

Independent services manage flight searches, hotel reservations, car rentals, and payments, allowing the system to query multiple external providers simultaneously.

Integration Platforms

crucial for enabling a company to communicate and share data smoothly among various management systems, apps, and services.

Integration Platforms

solutions offering planning, carrying

out, and managing integration functionalities (data

transformation, routing, security).

MIDA

MuleSoft Anypoint Platform

IBM Integration Bus

Dell Boomi

Apache Kafka

Examples of Integration Platforms

MuleSoft Anypoint Platform

A cutting-edge solution providing a centralized setting for API development and data integration.

IBM Integration Bus (IBM WebSphere)

A platform for enterprise integration that makes it easier for different applications to exchange and share information.

Dell Boomi

A cloud-based platform for integration compatible

with a wide variety of patterns and hybrid environments

Apache Kafka

A fault-tolerant, high-throughput, and real-time data streaming platform (a distributed event streaming system).

APoZaJi

Apache Camel

Postman

Zapier

Jitterbit

Examples of Integration Tools

Apache Camel

An open-source integration framework that simplifies the process of integrating multiple systems via a rich collection of connectors.

Postman

A popular API development and testing tool that makes it easier to test RESTful APIs.

Zapier

A no-code cloud platform allowing business users to automate workflows and link web apps using pre-built connections called "Zaps."

Jitterbit

An iPaaS solution that enables users to link applications, data, and devices, offering pre-built templates and a visual designer.