Introduction to a SOA adoption roadmap
Three analysis approaches
Service oriented analysis
Service oriented design
Introduction to service oriented patterns
Traditional EAI Approach
Problems With Traditional EAI Approach
Enter Service Oriented Architecture (SOA)
Build the Services
We Can Easily Change the Process
Change Flow Using Legacy Approach
Replacing an Application
From XML to Web Service to SOA
How SOA was done before
Emerging standards for SOA
Compare SOA with other architectures
What is SOA?
Creating a common understanding of SOA
The evolution of SOA
Introduce the concepts of services and SOA
Design principles of SOA
The relationship between SOA and web services
The advantages and risks of SOA
Why use models with SOA.
Difference between model and methodology.
Why use the Unified Modeling Language?
Introducing UML, the notation.
Identifying business processes.
Notation, Patterns and Methodology.
Which Methodology to choose?
Building from components.
What is an object?
Messages and methods.
Exercise: testing some basic concepts.
How a collection of services perform a task.
Simple request response interaction
Complex interaction involving many services.
Need for a coordinator service emerges.
Birth of orchestration or business process.
Composing processes using processes.
Business Process Execution Language (BPEL)
Example business processes
Basic web services elements
Core web services standards stack
The Importance of WSDL
The design of SOAP
The use of registries via UDDI
The basic concepts of service orientation
Aligning functional and nonfunctional requirements
The role of Intermediaries In Service Networks
Introductions to WS-* Extensions
Using UML to analyse and design interfaces
Generating a domain model
Implementing and realising Use Cases
Showing web service collaboration
Usage of communication diagrams
Legacy System Integration
Web Services to the Rescue
The role of ESB in SOA
Security and ESB
Service layer abstraction
Introduction to business process layer
Orchestration and choreography
The use WS-BPEL for process automation
Reference models and reference architectures
The IMPACT SOA reference model and architecture
SOA vendors and their relationship with SOA
SOA support in .NET and J2EE platforms
The layers pattern.
Classic three-their architecture.
Connecting to the domain layer.
Linking to the User interface.
Using packages to decompose a system.
Avoiding mutual dependencies.
What is layering and why we need them?
Application service layer
Business service layer
Orchestration service layer
The benefits of employing SOA
Review of common business goals
The risks associated with the SOA approach
Evaluating tradeoff strategies
02/01/2019: Microservices – some practical applications In today’s world you need to be able to quickly build and scale large applications – and microservice...
22/01/2018: The adoption of DevOps principles to achieve digital transformation calls for applications that can be developed quickly and efficiently, and...
23/10/2017: Debates on the present state of C++ in the programming world divide the participants into two camps: some dislike C++ and predict it's imminent...
19/10/2017: A leading Financial Services organisation was keen to get several of its teams working consistently in an "Agile" way. Agile is an iterative...
11/10/2017: The training was to target a team of developers, with a mix of Java, C# and some C++. The team made heavy use of Java SE with some elements of...
07/10/2017: This client had previously utilised third parties to develop and deliver its customer facing products and services. A strategy change required...
Bring a JBI course to your office
and train a whole team onsite
0800 028 6400 or request quote
0800 028 6400
Why JBI ?
"great technology tips"
"Access to exclusive content"
"Short course means less time off"
"Joined via web"
"Knowledgable sales staff"