文档下载 文档下载导航
设为首页 | 加入收藏
搜索 请输入内容:  
 导航当前位置: 文档下载 > 所有分类 > IT/计算机 > 电脑基础知识 > COMP5348_EnterpriseArchetecture_2014Semester1_COMP5348Week3And4TutorialDT
侵权投诉

COMP5348_EnterpriseArchetecture_2014Semester1_COMP5348Week3And4TutorialDT

University of Sydney_COMP5348_EnterpriseArchetecture_2014Semester1

Enterprise-Scale Software Development (COMP5348)

Semester 1, 2014

Tutorial Week 3 & 4 – Distributed Computing & Transactions

In your week 2 lab you looked at how transactions can be used to prevent lost updates, inconsistent reads and how they can facilitate rollback using a bank transfer example. The code sample in week 2 used a single process to execute a number of transactions between two accounts that had entries in the same database. In reality, account records might be spread across different servers at different bank branches. In this scenario, more than one server would be required to cooperate in completing a transfer operation. This is where distributed computing and distributed transactions enter the picture. In this week’s lab we will take a look at how to configure communications between separate (and potentially remote) processes, and in next week’s lab we demonstrate the use of distributed transactions to provide ACID properties in distributed environments. When you look through the solution available in the week 3 and 4 folder on eLearning, you’ll notice the components shown in Figure 1. Figure 1 below shows one possible distribution for the components:

Fig 1: Distributed Bank Deployment Diagram

For simplicity, in your lab, deployment of the components in Figure 1 will differ as follows:

1.

COMP5348_EnterpriseArchetecture_2014Semester1_COMP5348Week3And4TutorialDT

You’ll use only one database to store account details.

第1页

你可能喜欢

热门文档

相关文档

站点地图 | 文档上传 | 侵权投诉 | 手机版
本站所有资源均来自互联网,本站只负责收集和整理,均不承担任何法律责任,如有侵权等其它行为请联系我们.
文档下载 Copyright 2013 doc.guandang.net All Rights Reserved.  -  email