Download 分散式資訊系統 Project proposal

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts

Expense and cost recovery system (ECRS) wikipedia , lookup

PL/SQL wikipedia , lookup

Microsoft Access wikipedia , lookup

Database wikipedia , lookup

Relational model wikipedia , lookup

Concurrency control wikipedia , lookup

Microsoft SQL Server wikipedia , lookup

Versant Object Database wikipedia , lookup

Database model wikipedia , lookup

Clusterpoint wikipedia , lookup

Transcript
Distributed Information System
Term project proposal
R90725041 許巍瀚
R90725048 方祈鈞
Baseball Game Ticket
Reservation System
Motivation
I just went to a World Baseball Cup game. To
clinch a ticket was never easy, since I had to
be glued right in front of a 7-11 facsimile for
several hours.
Is there any easier way to get a ticket ?
2017/5/22
3
Goal
We hope to learn the skills concerned with
distribution system designing via the process
of implementing this project.
And thus, issues such as multi-threaded
programming, middleware, interface
definition language, and failure handling will
be presented in the project.
2017/5/22
4
Project Timeline
Proposal
Nov.19.2001
Learning
3 weeks
Implementation
3 weeks
Installation & Test
1 week
Project Due
Jan.4.2002
Demo
2017/5/22
?
5
System Structure Diagram
Replica
Database
Replica
Server
Server
Server
Dispatcher
End-users
2017/5/22
End-users
6
System Structure Diagram
Replica
Database
Replica
Server
Server
Server
Dispatcher
End-users
2017/5/22
End-users
7
System Description
Server side
Several servers, each is capable of receiving
numbers of request concurrently.
Thus, multi-threaded programming is required.
Client side
Users can use a browser-based web page to query
and book a reservation.
2017/5/22
8
System Description (cont’d)
Database
Information such as game date, teams, available
seat numbers, ticket price, etc. is saved in
database.
Synchronization among main database and
replicas must be achieved.
Dispatcher
Distribute requests over different servers.
2017/5/22
9
Rationale & Justification
Issues concerned with system designing
Scalability
Stability
Efficiency
Safety
Critical section
Numbers of ticket is limited
Several fans go for one ticket
Timestamp
2017/5/22
10
Alternatives Considered
Data replica
In case of network failure or system crash
Synchronization
Network failure handling
Fault tolerance
2017/5/22
11
System Requirement
3 servers.
1 main database and 2 replicas.
Servers and databases are linked with each
other.
2017/5/22
12
Implementation
Use JSP and GUI to implement user interface.
Use Microsoft SQL server.
Remote procedure calls and method
invocations are implemented with Java
Remote Method Invocation.
2017/5/22
13
Installation & Testing
Installation and testing will be finished in the
last week prior to the due date.
Testing within one component.
Inter-component testing.
Failure handling.
2017/5/22
14
Job Distribution
In principle, Hsu is responsible for the
database system, inclusive of construction of
database and communication among
databases.
Fang is responsible for the user interface,
sever maintenance, and flow control.
However, both of us will work together to
solve problems which we encounter.
2017/5/22
15