5 - Pub Sub Flashcards

1
Q

Advantages of client server

A

Easy
Thin clients

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

Drawbacks of client server

A

Interaction one to one
Each entitty must know how to address partner
Both must be available
Inherently synchronous
Only pull based

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

Pub Sub

A

Distributed Event based systems
Stores subscriptions and correctly delivers event notifs

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

Publishers (producers)

A

publish structured events to a service

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

Subscribers (consumers)

A

Register interest in particular events through subscriptions

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

Examples of Pub Sub

A

Live data broadcasting
Monitoring
Cooperation
Ubiquitous Computing

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

Characteristics of Pub/Sub system

A

Heterogeneous (distinct components can be made to work together)
Asynchronous

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

Space coupled

A

Comms directed to receiver

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

Space uncoupled

A

Sender does not need to know receiver identity

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

Time coupled

A

Receiver must exit at that time

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

Time uncoupled

A

Sender and receiver can have independent lifetimes

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

Channel based subscriptions

A

Subscribe to entire channel
Simple
No interplay between channels

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

Topic based subscriptions

(think about how the topics are laid out)

A

Topics organised hierarchically in subtree

Subscribing means receiving all messages to this node and below

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

Content based subscriptions

A

Subscribers define predicates (constraints) on attribute values of events

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

Event Schema

A

Un-typed set of typed attributes.

<attr-name, attr-type, attr-value>

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

Subscription Schema

A

A set of triplets of the form
<attr-name,attr-type,attr-value-predicate>

Specifies values of interest

17
Q

Centralised model

A

Central server acts as event broker

18
Q

Event matching steps

A

Subscription processing (index and store them)
Event processing (identify matched subscriptions)
Event delivery (to clients)

19
Q

Distributed Model

A

Sys of network of brokers.

Each local broker has its own matching engine

20
Q

Serverless - what is it and when is it used?

A

cloud native platform

short running, stateless computations
event-driven apps
scale up and down
charged by use

21
Q

When are cloud functions triggered

22
Q

Stateful vs Stateless

A

Apps that track state vs do NOT

23
Q

Why must states be kept separate to cloud functions?

A

Function instances are destroyed after use

24
Q

Advantages of serverless

A

Cheaper (at low use)
Scalable
More time devoted to user experience

25
Disadvantages of serverless
Vendor lockin Staff retraining to rearchitect apps
26
In large data scenarios, why might system and network delays affect real time alerts?
Lack of bandwitch, large data latency. Cannot reach aggregation point in time. Lack of scalability for processing large data