for Edge Services Presented By Fathiyeh Faghih

Transcription

1 University of Waterloo David R. Cheriton School of Computer Science Cloud Dt Data Management tcourse Application Specific Data Replication for Edge Services Presented By Fathiyeh Faghih Feb

2 Table of Content Architecture Motivation TPC-W Objects System Evaluation Conclusion Issues and Observations 2

3 Table of Content Architecture Motivation TPC-W Objects System Evaluation Conclusion Issues and Observations 3

4 Edge Services Architecture WAN LAN WAN 4

5 The Distributed Object Architecture + WAN + Edge Server Backend 5

6 The Distributed Object Architecture Client Client Client Client Client Client Edge Server WAN Backend Cluster 6

7 The Distributed Object Architecture Client Client Client Client Client Client Edge Server WAN Backend Cluster 7

8 Edge Server Architecture Frontend BLU ML DO DB 8

9 The Distributed Object Architecture Client Client Client Client Client Client Edge Server WAN Backend Cluster 9

10 Backend Cluster Architecture Frontend BLU ML DO DB 10

11 Table of Content Architecture Motivation TPC-W Objects System Evaluation Conclusion Issues and Observations 11

12 Motivation Encapsulating database access behind object specific interfaces Satisfaction of client requests locally Better response time Consistency maintenance according to the semantics of objects Encapsulation the complexity of data replication 12

13 Table of Content Architecture Motivation TPC-W Objects System Evaluation Conclusion Issues and Observations 13

14 TPC W Benchmark Feasibility of the edge services architecture for TPC-W Catalog Order Profile Inventory Best-seller-listseller list Frontend BLU DO DB ML 14

15 TPC W Benchmark Catalog Order Profile Inventory Best-seller-list 15

16 The Catalog Object Used for managing catalog information Abstraction of one-to-many updates Push-all update strategy (key, value) (key) Write Interface Read Interface Catalog 16

17 TPC W Benchmark Catalog Order Profile Inventory Best-seller-list 17

18 The Order Object Used for managing the propagation of completed orders Abstraction of many-to-one updates FIFO consistency (order, order sequence ID, edge server ID, message handler) Insert Interface Order 18

19 TPC W Benchmark Catalog Order Profile Inventory Best-seller-list 19

20 The Profile Object Used for handling reads/writes with low concurrency (User ID, field ID, value) (User ID) Write Interface Read Interface Profile 20

21 The Profile Object Semantics Low write/read ratio Sending the same user to the same edge server Using a write-any read-any policy Propagation of updates among all edge servers Conflict resolution using reconciliation rules 21

22 The Profile Object Availability Latency Relaxing consistency Simplicity it Increasing storage space and update bandwidth 22

23 TPC W Benchmark Catalog Order Profile Inventory Best-seller-list 23

24 The Inventory Object Used for a constraint enforcement Notification i of requesters, if the inventory is 0 Minimizing false positives (Numeric Value, Book ID ) Reserve Interface Inventory 24

25 The Inventory Object Inventory division among edge servers Keeping track of fthe edge servers inventories i by the backend server Re-distribution 25

26 The Inventory Object Availability Acceptable consistency System response time Limitationi i False positive 26

27 Table of Content Architecture Motivation TPC-W Objects System Evaluation Conclusion Issues and Observations 27

28 System Evaluation Performance Availability Consistency 28

29 System Evaluation Performance Availability Consistency 29

30 Performance Evaluation WAN LAN WAN WAN + + Edge Server Backend 30

31 System Evaluation Performance Availability Consistency 31

32 System Evaluation Performance Availability Consistency 32

33 Consistency Evaluation Examining the staleness of local inventory Unbalanced heavy workload 33

34 Table of Content Architecture Motivation TPC-W Objects System Evaluation Conclusion Issues and Observations 34

35 Conclusion Higher system availability and performance Specific application semantics A quantitatively evaluation of the distributed objects model 35

36 Table of Content Architecture Motivation TPC-W Objects System Evaluation Conclusion Issues and dobservations 36

37 Issues and Observations Need to developer s knowledge of the application s semantics Separation of semantics object from replication object as in the Globe system Consistency issues 37

38 38

39 Discussion 39

40 The Catalog Object Push-all update strategy FIFO consistency Time delays between occurrence of an update and its being seen. Concern Bandwidth No problem! Small writes/reads ratio 40

41 TPC W Benchmark Catalog Order Profile Inventory Best-seller-list 41

42 The Best Seller List Object Used for maintaining lists of best seller books Returning slightly stale information is better than stopping serving requests. (Subject ) Read Interface Best-Seller-List 42

43 The Best Seller List Object Availability System response time Minimizing communication Bandwidth consumption Monitoring all orders at the backend server 43