Karteikarten
Service Oriented Architecture III
Karten in diesem Stapel (34)
- 1E-Business Why learn the patterns?- IT architect is to evaluate business problems and build solutions to solve them
- The solutions can consist of one or more computer applications
- This approach enables architects to implement successful E-Business solutions - 2E-Business Key ElementsThe Patterns approach is based on a set of
layered assets:
- Business patterns that identify the interaction between users, businesses, and data
- Composite patterns that represent commonly occurring combinations of business patterns and integration patterns
- Runtime patterns that define the logical middleware structure supporting an application pattern - 3The Patterns for an E-Business Layered Asset Model
- 4Business PatternsDescribes the relationship between the users, the business, and the data
- 5Business Patterns 4 sub-patterns1) Self-service (user tot business)
2) Information Aggregation (user to data)
3) Collaboration (user to user)
4) Extended Enterprise (business to business) - 6Integration PatternsTies multiple business patterns together to solve a business problem
- 7Integration Patterns 2 Different Integrations1) Access Integration
2) Application Integration - 8Custom Design
- 9Composite Patterns- Electric Commerce
- Portal
- Account Access
- Trading Exchange
- Sell-side hub (supplier)
- Buy-side hub (purchaser) - 10Selecting Application PatternsAn application pattern has logical
components that describe a presentation tier
for interacting with users/application tiers - 11Selecting Application Patterns Goalbuild an efficient application
that allows users to access back-end
information - 12Selecting Application Patterns
- 13Selecting Application Patterns ExplanationPresentation Tier - handle communication with user
Application Tier - represent the component that handles access to the back-end applications and data
Multiple application boxes - represent the back-end applications that contain the business data - 14Runtime Patterns- Each function is associated with a Runtime Node
- In reality, these nodes exist on separate physical machines or can co-exist on the same machine - 15DIRECTLY INTEGRATED SINGLE CHANNEL APPLICATION PATTERN: RUNTIME PATTERN
- 16Product Mappings- To correlate real products with one or more Runtime nodes
- The product mappings are oriented towards a particular platform - 17Guidelines and related links Design guidelinesGuidelines for someone building the application
- 18Guidelines and related links Development GuidelinesTake someone through the process of building the
application - 19Guidelines and related links System management guidelinesAddress the
day-to-day operational concerns, e.g.
security, backup and recovery - 20Guidelines and related links Performance GuidelinesGive information on
how to improve the application and system
performance - 21Solution of Web Based Applications- Object Based Design
- Service Oriented Design
- Interface Based Design - 22Functional Elements of SOA
- 23SOA Functional Aspects1) Transport
2) Service Communication Protocol
3) Service Description
4) Service
5) Business Process
6) Service Registry - 24Functional Aspects TransportA mechanism to move service
requests from the service consumer to the
service provider, and service responses from
the service provider to the service consumer - 25Functional Aspects Service Communication ProtocolAn agreed
mechanism that the service provider and the
service consumer use for request/return - 26Functional Aspects Service DescriptionAn agreed schema for
describing what the service is, how it is
invoked, and what data is required - 27Functional Aspects ServiceDescribes an actual service that is
made available for use - 28Functional Aspects Business ProcessA collection of services,
in a particular sequence with a particular
set of rules, to meet a business requirement. - 29Functional Aspects Service RegistryA repository of service
and data descriptions to be used by service
providers to publish their services - 30Quality of Service Aspects- Policy
- Security
- Transaction
- Management - 31Quality of Service Aspects PolicyA set of conditions or rules under which a service provider makes the service available to consumers.
- 32Quality of Service Aspects SecurityThe set of rules that might be
applied to the identification, authorization,
and access control of service consumers
invoking services. - 33Quality of Service Aspects TransactionThe set of attributes that
might be applied to a group of services to
deliver a consistent result. - 34Quality of Service Aspects ManagementThe set of attributes that
might be applied to managing the services
provided or consumed.
Informationen
- Beschreibung
- Masters of Science Mobile App Karteikarten am Service Oriented Architecture III, erstellt von Nathan Hunsdale am 23/05/2014.
- Erstellt von
- Nathan Hunsdale
- Aufrufe
- 19
- Bewertung