Dependable Distributed Middleware Systems
18-749, Spring 2006
Team #: 1
Application: Su-Del-Ku -- A real-time, fault-tolerant, high performance game where two or more sudoku players can pit their intelligence against each other
Middleware + Platform: JBosss, MySQL, Linux
Team Members: Christopher
Nelson <crnelson@cs.cmu.edu>, Saul Jaspan <saul.jaspan@gmail.com>,
Lucia de Lascurain <ldelascu@andrew.cmu.edu>, Jose Luis Rios Trevino
<jriostre@andrew.cmu.edu>, Yudi Nagata <ynagata@andrew.cmu.edu>
2/11/2006:
Feedback on project proposal
MySQL on Linux working
JBoss on Linux working – need custom JBoss because of Lomboz
Group to send me an email with the quota that you need for JBoss and Eclipse
joinGameRoom to be the first end-to-end use case
Recommended to start with listGames instead because this is an end-to-end read-only method
Add a transaction id for every parameter and also in the database tables
Recommended to take a look at JNDI from previous years’ teams
Recommended to take a look at previous years’ teams with the same configuration
Don’t hard code port numbers
3/2/2006: Feedback on end-to-end use case
3/22/2006: Checkpoint 1 Presentation
Architecture very well described
Team is on top of things and has their implementation under control
Things to think about at this stage – where is most of your multithreading and concurrency? This will start to affect your performance in the last phase
Why did you need a callback, and how did you implement it? Are there alternatives?
Annotate the methods that you might not need if you go the stateless route
Identify which methods invoke the recovery mechanisms (e.g., setAsPrimary)
Have you played with the interceptor
as yet? Do you have a backup plan? I would recommend that you try a
simple “kill -9” script first and then go fancier – saves you
time
Baseline:
Failover:
Exception-handling:
Recovery:
Latency:
Performance:
Test-cases:
Additional features: