This document provides an overview of service-oriented architecture (SOA). It defines SOA as a design paradigm that specifies the creation of automation logic in the form of discrete, autonomous services. The key benefits of SOA include enabling flexible, federated business processes and optimization through reuse of services across organizations. The document discusses SOA concepts like loose coupling, service contracts, and different service types. It also outlines the layers of a service architecture and some core SOA principles.
It is a presentation of a research paper on Component Based Software Engineering vs Service Oriented Architecture. It deals with basic comparative study of CBSE and SOA , SOA technologies and Service Components, Modern Components. It also covers discussions and justifications of performance issues of web services.
This is a presentation of a research paper on comparative study of Component based Software Engineering and Service Oriented Architecture. It covers technologies of both paradigms as well as technical discussions and justifications on SOA. It also covers modern components.
Cloud Computing Model with Service Oriented ArchitectureYan Zhao
This presentation will discuss cloud computing from the evolution of service orientation point of view. It will discuss cloud computing models, the prior-arts, and the evolution path in federal government from Federal Enterprise Architecture, Service Oriented Architecture (SOA), and Service Oriented Infrastructure (SOI) or Federal Infrastructure Optimization Initiative, to Cloud Computing. It will also discuss the current trend of the new generation IT operating model, as well as the related business impact. While cloud computing is contributing to the enterprise evolution towards service orientation and shared services, appropriate business management and operation mechanisms must be in place in order to practice successfully, e.g. suitable business models, service models, service structure, funding models, operation models, operation structure, as well as lifecycle and governance. This presentation intends to provide a holistic view for the cloud computing evolution and shared service adoption in Federal Government.
It is a presentation of a research paper on Component Based Software Engineering vs Service Oriented Architecture. It deals with basic comparative study of CBSE and SOA , SOA technologies and Service Components, Modern Components. It also covers discussions and justifications of performance issues of web services.
This is a presentation of a research paper on comparative study of Component based Software Engineering and Service Oriented Architecture. It covers technologies of both paradigms as well as technical discussions and justifications on SOA. It also covers modern components.
Cloud Computing Model with Service Oriented ArchitectureYan Zhao
This presentation will discuss cloud computing from the evolution of service orientation point of view. It will discuss cloud computing models, the prior-arts, and the evolution path in federal government from Federal Enterprise Architecture, Service Oriented Architecture (SOA), and Service Oriented Infrastructure (SOI) or Federal Infrastructure Optimization Initiative, to Cloud Computing. It will also discuss the current trend of the new generation IT operating model, as well as the related business impact. While cloud computing is contributing to the enterprise evolution towards service orientation and shared services, appropriate business management and operation mechanisms must be in place in order to practice successfully, e.g. suitable business models, service models, service structure, funding models, operation models, operation structure, as well as lifecycle and governance. This presentation intends to provide a holistic view for the cloud computing evolution and shared service adoption in Federal Government.
Hierarchical Digital Twin of a Naval Power SystemKerry Sado
A hierarchical digital twin of a Naval DC power system has been developed and experimentally verified. Similar to other state-of-the-art digital twins, this technology creates a digital replica of the physical system executed in real-time or faster, which can modify hardware controls. However, its advantage stems from distributing computational efforts by utilizing a hierarchical structure composed of lower-level digital twin blocks and a higher-level system digital twin. Each digital twin block is associated with a physical subsystem of the hardware and communicates with a singular system digital twin, which creates a system-level response. By extracting information from each level of the hierarchy, power system controls of the hardware were reconfigured autonomously. This hierarchical digital twin development offers several advantages over other digital twins, particularly in the field of naval power systems. The hierarchical structure allows for greater computational efficiency and scalability while the ability to autonomously reconfigure hardware controls offers increased flexibility and responsiveness. The hierarchical decomposition and models utilized were well aligned with the physical twin, as indicated by the maximum deviations between the developed digital twin hierarchy and the hardware.
Immunizing Image Classifiers Against Localized Adversary Attacksgerogepatton
This paper addresses the vulnerability of deep learning models, particularly convolutional neural networks
(CNN)s, to adversarial attacks and presents a proactive training technique designed to counter them. We
introduce a novel volumization algorithm, which transforms 2D images into 3D volumetric representations.
When combined with 3D convolution and deep curriculum learning optimization (CLO), itsignificantly improves
the immunity of models against localized universal attacks by up to 40%. We evaluate our proposed approach
using contemporary CNN architectures and the modified Canadian Institute for Advanced Research (CIFAR-10
and CIFAR-100) and ImageNet Large Scale Visual Recognition Challenge (ILSVRC12) datasets, showcasing
accuracy improvements over previous techniques. The results indicate that the combination of the volumetric
input and curriculum learning holds significant promise for mitigating adversarial attacks without necessitating
adversary training.
Explore the innovative world of trenchless pipe repair with our comprehensive guide, "The Benefits and Techniques of Trenchless Pipe Repair." This document delves into the modern methods of repairing underground pipes without the need for extensive excavation, highlighting the numerous advantages and the latest techniques used in the industry.
Learn about the cost savings, reduced environmental impact, and minimal disruption associated with trenchless technology. Discover detailed explanations of popular techniques such as pipe bursting, cured-in-place pipe (CIPP) lining, and directional drilling. Understand how these methods can be applied to various types of infrastructure, from residential plumbing to large-scale municipal systems.
Ideal for homeowners, contractors, engineers, and anyone interested in modern plumbing solutions, this guide provides valuable insights into why trenchless pipe repair is becoming the preferred choice for pipe rehabilitation. Stay informed about the latest advancements and best practices in the field.
Hybrid optimization of pumped hydro system and solar- Engr. Abdul-Azeez.pdffxintegritypublishin
Advancements in technology unveil a myriad of electrical and electronic breakthroughs geared towards efficiently harnessing limited resources to meet human energy demands. The optimization of hybrid solar PV panels and pumped hydro energy supply systems plays a pivotal role in utilizing natural resources effectively. This initiative not only benefits humanity but also fosters environmental sustainability. The study investigated the design optimization of these hybrid systems, focusing on understanding solar radiation patterns, identifying geographical influences on solar radiation, formulating a mathematical model for system optimization, and determining the optimal configuration of PV panels and pumped hydro storage. Through a comparative analysis approach and eight weeks of data collection, the study addressed key research questions related to solar radiation patterns and optimal system design. The findings highlighted regions with heightened solar radiation levels, showcasing substantial potential for power generation and emphasizing the system's efficiency. Optimizing system design significantly boosted power generation, promoted renewable energy utilization, and enhanced energy storage capacity. The study underscored the benefits of optimizing hybrid solar PV panels and pumped hydro energy supply systems for sustainable energy usage. Optimizing the design of solar PV panels and pumped hydro energy supply systems as examined across diverse climatic conditions in a developing country, not only enhances power generation but also improves the integration of renewable energy sources and boosts energy storage capacities, particularly beneficial for less economically prosperous regions. Additionally, the study provides valuable insights for advancing energy research in economically viable areas. Recommendations included conducting site-specific assessments, utilizing advanced modeling tools, implementing regular maintenance protocols, and enhancing communication among system components.
Welcome to WIPAC Monthly the magazine brought to you by the LinkedIn Group Water Industry Process Automation & Control.
In this month's edition, along with this month's industry news to celebrate the 13 years since the group was created we have articles including
A case study of the used of Advanced Process Control at the Wastewater Treatment works at Lleida in Spain
A look back on an article on smart wastewater networks in order to see how the industry has measured up in the interim around the adoption of Digital Transformation in the Water Industry.
Water Industry Process Automation and Control Monthly - May 2024.pdf
soa ppt v7.ppt
1. Service Oriented Architecture
Dr. V. Prasanna Venkatesan
Professor
Department of Banking Technology
Pondicherry University
Pondicherry, India – 605 014
prasanna _v@yahoo.com
3. Introduction to SOA
“Information technology and business are
becoming inextricably interwoven. I don't
think anybody can talk meaningfully about one
without the talking about the other.”
7. Current IT Infrastructure
Lacks agility to keep up with business
objectives
Places limitations on Business
Requirements change
Interpretations often inaccurate or limited
Lengthy development cycles inflexible to
change
Implementations “cast in concrete”
8. Majority of solutions have been created by
identifying the business tasks
defining their business requirements
building the corresponding solution logic
Change in requirements
modify existing solution
• Not Efficient
• Results in Complex Infrastructures and
complicated Enterprise Architectures
• Integration becomes a Challenge
Current IT Infrastructure
9. majority of solutions have been created by
identifying the business tasks
defining their business requirements
building the corresponding solution logic
Change in requirements
modify existing solution
build a new application altogether
Current IT Infrastructure
• Highly Wasteful
• Inflates an Enterprise
10. The Way out is to…
Go with an enterprise technology solution that
promises agility and flexibility
Leverage integration process through composition
of services spanning multiple enterprises
11. The Way out is to…
Think about business outcomes as
a set of composed services
instead of monolithic applications
12. SOA Concepts
“SOA will be a prevailing software
engineering practice, ending the 40-year
domination
of monolithic software architecture.”
13. The Solution is…ServiceOrientation
SO is a design paradigm that
specifies the creation of
automation logic in the form
of services
Service refers to a discretely
defined set of contiguous
and autonomous business or
technical functionality
SO is applied as a strategic
goal in developing a Service-
Oriented Architecture (SOA).
Services are trees
SO is the Forest
14. The Solution is…ServiceOrientation
Access software via Services that are easy to
find and connect to
Provide a standard way of building and
accessing Services
Build applications out of Services
15. Wasn’t there SOA before?
SOA have been around a while
CORBA (Common Object Request Broker
Architecture)
DCOM (Microsoft Distributed Component
Object Model)
16. Why is it different?
SOA reflects the reality of ownership
boundaries
CORBA, RMI, COM, DCOM, etc. all try to
implement transparent distributed systems
Ownership is of the essence in SOA
SOA is task oriented
Components are organized by s/w function
Services are organized by business function
SOA is inspired by human organizations
Component concepts are technology-oriented
Services worked for us, it should work for
machines
17. So… What is SOA ?
SOA is a conceptual business architecture
where business functionality or application logic
is made available to SOA users, or consumers
as shared reusable services on an IT network
[Source: SOA: A planning and implementation guide for business and
technology by Eric A. Marks, Michael Bell]
18. So… What is SOA ?
[Source: IBM ]
An SOA is an orchestrated sequence of
messaging, transformation, routing and
processing events in which XML
technologies expose the message
content and the components that
operate on the messages
19. SOA- Roles & Functions
Service Consumer :
Discover services and
metadata from Service
Registry
Service Producer :
Publish newly developed
services and artifacts
Service Registry : Notify
clients of changes
Organize service metadata
with classification and
lifecycle support (Broker)
21. Service Architecture
Service
Service
Service
Service
Finance
Distribution
Manufacturing
Supply
Service virtualizes how that capability is
performed, and where and by whom the
resources are provided, enabling multiple
providers and consumers to participate
together in shared business activities.
Multiple Service Consumers
Multiple Business Processes
Multiple Discrete Resources
Multiple Service Providers
source:TietoEnator AB,
Kurts Bilder
Business scope
SOA structures the business and its systems
as a set of capabilities that are offered
as Services, organized into a Service
Architecture
Shared
Services
Service Centric
23. Why SOA?
To enable Flexible, Federated Business Processes
Enabling a virtual federation of
participants to collaborate in an
end-to-end business process
Enabling alternative
implementations
Enabling reuse of
Services
Enabling virtualization of business resources Enabling aggregation from multiple
providers
Identification
Ticket Sales
Ticket Collection
Inventory
Logistics
Manufacturing
Availability
Service
Service
Service
Service Service
Service
Service
Service
Service
Service
Ordering
source:TietoEnator AB,
Kurts Bilder
24. Why SOA? To enable Business Process Optimization
and the Real Time Enterprise (RTE)
Seamless End to End Process
Internal Systems
SOA Pattern: Standardized Service
provided by multiple suppliers
Service from Multiple Suppliers
SOA Patterns: Single, Multi-Channel
Service for consistency
BPM Expressed in
terms of Services
Provided/Consumed
Enterprise
source:TietoEnator AB,
Kurts Bilder
Smart Clients
Stores POS
Mobile
3rd Party Agents
Portal
Service to Customers
25. Why SOA?
Enable Structural Improvement
ERP X Process Z Partner A Process Y
Service
Standardizing capabilities Information Consistency
Policy Consistency
e.g. Single Customer
Details Service
Consolidation/
Selection
process
Reducing impact
of change
Encapsulating
implementation
complexity
ERP Z
CRM
System 2
CRM
System 1
Product
System
Policy Rationalization and Evolution
Resource Virtualization
e.g. Multiple Sources
of Customer Details
26. SOA Defined
SOA is a software architecture model
in which business functionality are logically grouped and encapsulated
into
self contained,
distinct and reusable units
called services that
represent a high level business concept
can be distributed over a network
can be reused to create new business applications
contain contract with specification of the purpose, functionality,
interfaces (coarse grained), constraints, usage
... of the business functionality
Services are autonomous, discrete and reusable units of business functionality exposing its
capabilities in a form of contracts.
Services can be independently evolved, moved, scaled even in runtime.
27. What is Service Architecture?
• A collection of services
• classified into types
• arranged into layers
• Governed by architectural
patterns and policies
services
type type
type
source:TietoEnator AB,
Kurts Bilder
29. SOA is an evolutionary step
for architecture
30. SOA is an evolutionary step
in reusability and communication
31. SOA is an evolutionary step
Project-ware SOA
EAI
in distributed communications
source:Sam Gentile
32. Service Architecture Organized by Layers
Reasons for Layering
1. Flexible composition.
2. Reuse.
3. Functional standardization in lower
levels
4. Customization in higher layers
5. Separation of Concerns.
6. Policies may vary by Layer
Example Layers
Presentation
& workflow
Composed Services
Basic Services
Underlying
API
according to:TietoEnator
AB, Kurts Bilder
33. Major service types
Basic Services:
Data-centric and logic-centric services
Encapsulate data behavior and data model and ensures
data consistency (only on one backend).
Basic services are stateless services with high degree of
reusability.
Represent fundamental SOA maturity level and usually are
build on top existing legacy API (underlying services)
Composed Services :
expose harmonized access to inconsistent basic services
technology (gateways, adapters, façades, and functionality-
adding services).
Encapsulate business specific workflows or orchestrated
services.
34. Service Types
Foundation
Service Blocks
Core APIs
G
eo
M
edia
Terra
Share
G
/
T
e
c
h
I/C
A
DI
/
.
.
In
Service Other
S
e
r
v
i
c
e
I
n
f
r
a
s
t
r
u
c
t
u
r
e
B
a
s
i
c
S
e
r
v
i
c
e
s
C
o
m
p
o
s
i
t
e
S
e
r
v
i
c
e
s
Smart Client
P
o
r
t
a
l SOA Management & Security
service mediation, routing, trust
enablement. ESB, Service Registry
Multi channel applications: Mobile,
Smart, Thin, Thick clients, Portals.
Business centric services,
orchestrated workflows.
Intermediate services (gateways,
facades )
Data centric and logic
centric consistent services.
Highly reusable, stateless
servers
Business
Capabilities
36. Standardized Service Contracts
“Services within the same service inventory
are in compliance with the same contract
design standards."
Services use service contract to
Express their purpose
Express their capabilities
Use formal, standardized service contracts
Focus on the areas of
Functional expression
Data representation
Policy
Source: Thomas Erl
37. Loose Coupling
“Service contracts impose low
consumer coupling requirements
and are themselves decoupled
from their surrounding
environment."
Create specific types of
relationships within and outside of
service boundaries with a
constant emphasis on reducing
(“loosening”) dependencies
between
Service contract
Service implementation
Service consumers Source: Thomas Erl
38. Abstraction
“Service contracts only contain essential information and information
about services is limited to what is published in service contracts”
Avoid the proliferation of unnecessary service information, meta-
data.
Hide as much of the underlying details of a service as possible.
Enables and preserves the loosely coupled relationships
Plays a significant role in the positioning and design of service
compositions
Source: Thomas Erl
39. Reusability
“Services contain and express agnostic logic and can be
positioned as reusable enterprise resources."
Reusable services have the following characteristics:
Defined by an agnostic functional context
Logic is highly generic
Has a generic and extensible contract
Can be accessed concurrently
Source: Thomas Erl
40. Autonomy
"Services exercise a high level of control over their
underlying runtime execution environment."
Represents the ability of a service to carry out its
logic independently of outside influences
To achieve this, services must be more isolated
Primary benefits
Increased reliability
Behavioral predictability
Source: Thomas Erl
41. Statelessness
"Services minimize resource consumption by deferring the
management of state information when necessary."
Incorporate state management deferral extensions within a service
design
Goals
Increase service scalability
Support design of agnostic logic and improve service reuse
Source: Thomas Erl
42. Discoverability
"Services are supplemented
with communicative meta data
by which they can be effectively
discovered and interpreted."
Service contracts contain
appropriate meta data for
discovery which also
communicates purpose and
capabilities to humans
Store meta data in a service
registry or profile documents
Source: Thomas Erl
43. Composability
"Services are effective
composition participants,
regardless of the size and
complexity of the composition."
Ensures services are able to
participate in multiple
compositions to solve multiple
larger problems
Related to Reusability principle
Service execution should efficient
in that individual processing
should be highly tuned
Flexible service contracts to allow
different types of data exchange
requirements for similar functions Source: Thomas Erl
44. The Promise of SOA
The Discoverable feature enables
Faster decision cycles
Increase cross-organizational information visibility
Precision information retrieval
Location Transparency
Standards Based and Highly Interoperable
capability achieves
Platform and language independent
Leverage existing IT investments: Lower Cost
Heterogeneity
45. The Promise of SOA
Loosely Coupled and Decentralized nature
provides
Plug and play components independent of
platform
Enable redundancy for survivability
Emphasis on business logic and less on
plumbing
Reduced overall system complexity
System Composability
47. Security in SOA
Security is a pressing issue in SOAs
SOA stresses machine-to-machine
interaction
IT security is based on human-to-machine
interaction.
Authentication and authorization become
more challenging in this environment.
48. Unsecured SOA
architecture's open nature
hackers with the ability to eavesdrop and
reroute it or transform its content for
purposes of mischief or fraud
Cannot secure unknown third parties
Vulnerable to overload.
Security in SOA (Contd)
49. No transaction logging
Cannot keep track of its users or its
messages.
No auditable record of usage that can be
used to investigate security problems or
diagnose security weaknesses.
Security in SOA (Contd)
50. SOA Security Solution
SOA security solution that enables
Message monitoring
Federated authentication
Application proxy
Contract management
Certificates, keys, and encryption and
Audit logging
Even though it looks like a long list, but the truth
is without any one of these in place, all the
benefits from SOA will evaporate.
52. How might SOA transform an
organization?
Building New Solutions With Services
Independent Pieces Within Applications
Independent Development and Maintenance
Scale-Out
Slicing Apart Existing Apps
separate the “Big Ball of Mud”
Joining Together Existing Apps
Connectivity
B2B: Business-to-Business
EAI: Enterprise Application Integration
Business Process
54. SOA – Non applicable scenarios
Stable or homogeneous enterprise IT
environment
Organization that does not offer or use software
functionality as services to and from external
parties
Real time requirements that need synchronous
communications
55. Case Study – E-Banking
“Change is such hard work.”
56. Case study – E-banking
Bank offers various financial services such as
Online banking
Bill payments
Brokerage, etc.,
Financial services are accessible through variety of
channels like
Branch offices
ATMs
Call centers
E-mails
Internet
A Service Oriented Computing Model for E-Banking
handles the agile scenarios of e-banking system
58. Case study – E-banking
Customer Regulatory
bodies
Branch Other banks
Core
financial
services
Payments
services
Mutual
fund
services
Bill payment,
presentment
services
Alerts and
messaging
services
Security
Services
Service
Broker
Service
Manager
SA
Agent
Service Registry Bank Server Knowledge
repositories
E-Banking Service Layer
Business
Layer
App.
Layer
Data
Layer
Service Management Layer
59. Application layer
Illustrates client applications specific to
Individual customers
Corporate customers
Self-supportive services for branch offices,
different section offices, etc.,
Regulatory bodies and
Other banks
Takes advantage of services provided by
e-banking system
60. Business layer
Set of components that constitute the actual
e-banking system
E-banking service layer acts as the mediator
between client applications and the rest of the
system
Service management layer is responsible for
generating and coordinating all the messages
within the system
61. E-banking Service Layer
Core financial services
Payments services
Mutual fund services
Bill payment & presentment services
Alerts and messaging services
Security Services
62. Service Management layer
Service Broker receives service requests and
discover the services
Service Manager is responsible for service life cycle
management
Service Advisory Agent generate suggestions of
composition alternatives
63. Data layer
Sources of information that support the e-
banking system
Service Registry
Data server
Knowledge Repository
65. Future State of SOA
Combining mature technology with a proven
methodology will allow organizations to
transit from traditional enterprise automation
logic to SOA-based which achieve long-term
SOA benefits.
The future state of SOA has the potential of
creating a new breed of “agile organization”.
66. References
www.soasystems.com
www.serviceorientation.org
www.ibm.com/soa
Eric A. Marks, Michael Bell, “SOA: A planning and
implementation guide for business and technology”, John Wiley
& Sons -2006
Tony Chao Shan, “Building a service oriented eBanking
platform”, Proceedings of the 2004 IEEE International
Conference on Services Computing (SCC’04)