4.1.2 – Service Principles

Loading...

來自 University of Alberta 的課程

Service-Oriented Architecture

70 個評分

University of Alberta

Service-Oriented Architecture

70 個評分

課程 4（共 4 門，Specialization Software Design and Architecture）

Based on an understanding of architectural styles, you will review architectures for web applications, then explore the basics of Service-Oriented Architecture (SOA) in two approaches: Web Services (WS*) and Representational State Transfer (REST) architecture. In the Capstone Project you will connect a Java-based Android application with Elasticsearch, a web service with a REST application programmer interface (API). After completing this course, you will be able to: • Describe SOA (Service-Oriented Architecture) to structure web-based systems. • Explain WS* services (i.e., SOAP over HTTP, WSDL, UDDI, BPEL). • Apply REST architecture (i.e., JSON over HTTP, URI). • Identify REST design principles. • Create a system using REST interfaces. • Apply microservice architecture.

從本節課中

Web Technologies

In this module, we will introduce you to service-oriented architectures and their basic principles. Then, you will get a crash course on the technologies that underpin the Web, so that you are ready to learn about web services in the next module. This module also covers some earlier precursors of service-oriented architecture.

4.1.1 – Introduction to Service-Oriented Architecture13:15

4.1.2 – Service Principles3:09

4.1.3 - Web Systems Evolution8:26

4.1.4 – Web Systems Architecture5:24

4.1.5 – HTML / XML / JSON5:04

4.1.6 – HTTP12:02

4.1.7 – JavaScript4:52

4.1.8 – Remote Procedure Call (RPC)14:27

4.1.9 – Object Brokers12:40

與講師見面

Kenny Wong
Associate Professor
Computing Science, Faculty of Science

[MUSIC]

In order to provide services that are useful and reusable there

are best practices for services and service oriented architectures.

These various best practices, guidelines, and principles all tend to touch on

the desirable properties of services in a service oriented architecture.

So let's talk about what those desirable properties are.

Modular, services should be modular and

loosely coupled, this gives them the property of being reusable and combinable.

Services are meant to be mixed and matched.

In object oriented programming, loose coupling is achieved by only exposing

the relevant elements of a class or component to its client.

In service oriented architecture, requests are made by passing communication to

the service in a way that aligns with its interface.

The service performs the necessary operations then passes back

a communication containing the results of the service or

a confirmation that the request was fulfilled.

We will see that this can look quite similar to a method call,

having a named operation and relevant parameters.

It can also be more like a document that embodies a request with the content of

the document including the information that the service provider needs.

Composable, services can and

should be used in combination to create usable applications or other services.

In order to be composable the services must be modular.

Using services in combination is like composing objects in an object

oriented programming paradigm.

Just like objects can be combined to provide the desired behavior so

too can services in SOA.

Platform- and Langugage-Independent, a good service is platform- and

language-independent.

For example,

a service which is coded in Java can be used by a service requester coded in Ruby.

Platform and language-independence is achieved by following

communication standards and protocols.

In the case of services on the Internet,

services are often requested with an XML file or an HTTP request.

The key to coordinating services on different platforms or

in different languages is enforcing well defined communication.

Self-describing, a service should describe how to interact with it.

In other words, it describes its own interface.

This includes what input it takes and what output it gives.

There are formal standards for describing services.

Using WSDL, which stands for web services description language.

We will talk more about WSDL later in the course.

Self-Advertising, in order to say service,

potential clients must know what is available.

In house organizations may catalog their surfaces in any way that works for

their business.

Distributed applications using web services have standards like UDDI,

which stands for Universal Description, Discovery and

Integration to connect service providers with potential service requesters.

Services can be used in different ways.

In the context of large organizations providing services for different business

units or over the Internet where anyone can provide or use a software service.

No matter where or how services are deployed the properties we talked about

are essential for effective services and service oriented architectures.

探索我們的目錄

免費加入並獲得個性化推薦、更新和優惠。

Coursera 致力於普及全世界最好的教育，它與全球一流大學和機構合作提供在線課程。

© 2018 Coursera Inc. 保留所有權利。

通過 App Store 下載

通過 Google Play 獲取