Lecture 3: SOAP, REST & FaaS Flashcards

1
Q

SOAP

A
  • Transmitting information (relies on XML)
  • Light weight
  • Extensible
  • Allows security, routing and reliability
  • Interoperable
  • Independent (any programming language allowed, any number of message exchange patterns (MEPs))
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What is WSDL in one sentence?

A
  • Interface description (describing functionality of web service)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

SOAP Message Format

A
  • SOAP Envelope
  • SOAP Header
  • SOAP Body
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

WSDL describes:

A
  • What a service’s interface looks like
  • How a service is accessed
  • Where a service is located
  • Contract between provider and consumer of service
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

WSDL does not describe:

A

Computations and semantics

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

WSDL Characteristics

A
  • Platform- and language- independence
  • Schema validated
  • Division of interface description and technical details
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

REST stands for:

A

Representational State Transfer

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Why is WSDL outdated?

A
  • Popularity of REST

- Easiness of REST

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

REST Elements

A
  • Components (client, service)
  • Connectors (HTTP, request/reply)
  • Data (resources, representations)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

REST Design Decisions

A
  • Ignores component implementation details.

- Focus on the roles of the components, their interactions and their interpretation of data elements.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Core data elements in REST:

A
  • Resource
  • URI (Uniform Resource Identifier)
  • Representational (HTML webpage)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Core actions REST

A
  • Create: HTTP POST
  • Retrieve: HTTP GET
  • Update: HTTP PUT
  • Delete : HTTP DELETE
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

REST Characteristics

A
  • Cache
  • Stateless
  • Pull-based interaction style
  • Named resources
  • Interconnected resource representations
  • 4 HTTP methods
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

REST vs WS-*

A
  • REST is more lightweight, more scalable, and more easy to integrate on the web
  • SOAP & WSDL are better for security and for integrating enterprise information systems
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

FaaS

A
  • Stateless
  • Triggered by event
  • Auto-scalable
  • Serverless computing
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Serverless computing

A
  • Offloads responsibility for common infrastructure management tasks to cloud provides and allows engineers to focus on business logic
  • Never pay for idle capacity
17
Q

Key point FaaS

A

Worker serves the request and then the function is underplayed (stateless), that’s how you minimise resource consumption