دانلود فایل

فروشگاه فایل و پاور پوینت آماده

پاور پوینت (اسلاید) معماري سرويس گرا ()

پاور پوینت (اسلاید) معماري سرويس گرا ()  با سلام

فایل معماري سرويس گرا () یک پاورپوینت بسیار عالی در 47 اسلاید می باشد این PowerPoint بر اساس استاندارد های اصلی طراحی پاورپوینت آماده و تنظیم شده است؛ این فایل دارای طراحی بسیار عالی و چشم نواز می باشد.
شما با استفاده ازاین پاورپوینت میتوانید یک ارائه بسیارعالی و با شکوهی داشته باشید و همه حاضرین با اشتیاق به مطالب شما گوش خواهند داد.

لطفا نگران مطالب داخل پاورپوینت نباشید، مطالب داخل اسلاید ها بسیار ساده و قابل درک برای شما می باشد، ما عالی بودن این فایل رو تضمین می کنیم.



محتواب برخی از اسلاید ها :


توجه داشته باشید هرگونه بهم ریختگی در متن زیر در اثر کپی کردن از پاورپوینت می باشد و در فایل پاورپوینت اصلی هیچ اشکال و به هم ریختگی وجود ندارد

4

In the Beginning …Computers were the domain of scientists for scientists
Business and Government discovered the value of computing
Business requirements needed to be captured and programmed

5

Some Past Attempts …COBOL – It was designed to be business-problem oriented, machine-independent, and capable of continuous change and development.
SQL – The SQL "language" allows anyone with a computer terminal to access and use relational databases. Originally thought to be an end-user tool.
SAD – Structured Analysis and Design (Yourdon/DeMarco)
IE – Information engineering (design by pictures) James Martin
OOAD – Object-Oriented Analysis and Design

6

Revolution …Revolution
COBOL
Basic programming language
C programming language
SQL
Structured analyses and design
Electronic data exchangeEvolution
Web Services
Information Engineering
CASE
C++
Java
Object-Oriented Analysis and Design
HTML
Common Record (XML)
Ecosystem
Standards
SOA

What is Service-Oriented Architecture

8

What is Service-Oriented ArchitectureService-Oriented Architecture (SOA) is an architectural style. Applications built using an SOA style deliver functionality as services that can be used or reused when building applications or integrating within the enterprise or trading partners.

9

SOAUses open standards to integrate software assets as services
Standardizes interactions of services
Services become building blocks that form business flows
Services can be reused by other applications

10

What is a ServiceA service is a reusable component that can be used as a building block to form larger, more complex business-application functionality.
A service may be as simple as “get me some person data,” or as complex as “process a disbursement.”

11

What is a ServiceA service provides a discrete business function that operates on data. Its job is to ensure that the business functionality is applied consistently, returns predictable results, and operates within the quality of service required.

12

What is a ServiceHow the service is implemented, and how a user of the service accesses it, are limited only by the SOA infrastructure choices of the enterprise.
From a theory point of view, it really doesn’t matter how a service is implemented.

13

Characteristics of a ServiceSupports open standards for integration: Although proprietary integration mechanisms may be offered by the SOA infrastructure, SOA’s should be based on open standards. Open standards ensure the broadest integration compatibility opportunities.

14

Characteristics of a ServiceLoose coupling: The consumer of the service is required to provide only the stated data on the interface definition, and to expect only the specified results on the interface definition. The service is capable of handling all processing (including exception processing).

15

Characteristics of a ServiceStateless: The service does not maintain state between invocations. It takes the parameters provided, performs the defined function, and returns the expected result. If a transaction is involved, the transaction is committed and the data is saved to the database.

16

Characteristics of a ServiceLocation agnostic: Users of the service do not need to worry about the implementation details for accessing the service. The SOA infrastructure will provide standardized access mechanisms with service-level agreements.

17

Legacy Business Process

18

Architectural Choke PointMonolithic
Extremely complex
Very tightly coupled
Difficult to find clean integration points
Lack of standards makes it difficult to integrate
Rigid architecture makes even small changes complex and costly

19

SOA Business Process

How Do You Build a Service-Oriented Architecture Solution

21

IT Infrastructure is an EcosystemCOBOL
C++
Java
J2EE
Networks
TCP/IP
Web Service
Mid-Tier Servers.NET
Messaging
HTML
Operating Systems
CICS
Routers
Databases
Mainframes

22

Managing the EcosystemTechnology Management
Product duplication
Standards
Product/Vendor lock-in
Support skill setsVersion Management
Managed Evergreening
Limited versions in production

23

Legacy Integration

24

SOA Integration

25

Integration StackIndustry Standards

Language Standards

Custom API’s

Native Interfaces

Enterprise Service Bus

27

What is an Enterprise Service Bus (ESB)An enterprise service bus is an infrastructure used for building compound applications
The enterprise service bus is the glue that holds the compound application together
The enterprise service bus is an emerging style for integrating enterprise applications in an implementation-independent fashion
An enterprise service bus can be thought of as an abstraction layer on top of an Enterprise Messaging System

28

Key Characteristics of an ESBStreamlines development
Supports multiple binding strategies
Performs data transformation
Intelligent routing
Real time monitoring
Exception handling
Service security

29

What is an ESBIn its simplest form:
An ESB delivers a message from one point to another.
Don’t EAI’s already do this

30

EAI LimitationsAn EAI can be a tightly coupled solution
An EAI can be location-specific
An EAI can be based on proprietary transport technology

31

Let’s Walk Through the ESBGet Person Data
Use Standard Student Identification Method (SSIM) identifiers to find the person
Return the Person Data

This is a fictional-use case, and is only intended to illustrate how an ESB would provide a service.

32

The ESB BoundariesThe ESB (in its simplest form) is responsible for getting a message from point A to point B.

33

Get the Message on the BusA binding component “speaks” the service’s protocol, which happens to be SOAP over JMS.

34

Perform the Person ReadThe request is now routed to the Get Person Data Service, which will perform the business logic.

35

Do the SSIM LookupA call is made to the SSIM service to perform a lookup of the Student Identifier (SID). The SSIM service lives inside the bus.
Note: The SSIM binding components are not shown so the diagram can remain simple.

36

Return the Person DataThe process is reversed, returning the response to the requester.

37

ESB SummaryLoose Coupling
Location Transparency
Transport Neutral

38

Defining the MessageWeb Services Description Language
Open Standard for describing Interfaces to Services (http://www.w3.org/TR/wsdl)
Characteristics
Describes data expected to be sent and received
Describes what the service can do
Describes how to reach the service
WSDL description is an XML document

39

Message-Exchange PatternsOne-way. The endpoint receives a message.
Request-response. The endpoint receives a message, and sends a correlated message.
Solicit-response. The endpoint sends a message, and receives a correlated message.
Notification. The endpoint sends a message.

Building a Compound Application

لطفا در خرید این فایل تردید نکنید
روی دکمه پرداخت در زیر کلیک کنید

پرداخت هزینه و دریافت فایل

مبلغ قابل پرداخت 2,350 تومان
نمایش لینک دانلود پس از پرداخت هزینه
ایمیل
موبایل

درصورتیکه برای خرید اینترنتی نیاز به راهنمایی دارید اینجا کلیک کنید


پرداخت اینترنتی - دانلود سریع - اطمینان از خرید

فایل هایی که پس از پرداخت می توانید دانلود کنید

نام فایلحجم فایل
4729_2000693_3101.zip811.8k