Henry Naftulin wrote:It looks like the thread for Horizontal scaling got side conversation on what is Reliability is, so I figured this topic deserves its own thread.
So is reliability = correctness + availability or is it something else?
Heading to part 3 exam tomorrow, so it would be great to hear your thoughts and any tips on part 3
Meeti Khare wrote:Thanks Rohid,
But somehow i did not feel that Cade's book has given proper example, or may be I could not understand it.
can you please elaborate on this "something else" ?
rohid dev wrote:You can use JMS for synchronous messaging.
Also 5 sec response time is possible depends upon the resources used
The receive method can be used in several ways to perform a synchronous receive. If you specify no arguments or an argument of 0, the method blocks indefinitely until a message arrives:
Message m = queueReceiver.receive();
Message m = queueReceiver.receive(0);
For a simple client program, this may not matter. But if you do not want your program to consume system resources unnecessarily, use a timed synchronous receive. Do one of the following:
Call the receive method with a timeout argument greater than 0:
Message m = queueReceiver.receive(1); // 1 millisecond
For SCEA part 2 - make sure you have specified all your assumptions.
Madhu Maniganta wrote:Jeanne,
I too thought of showing DAOs in my class diagram, but was confused after looking at Cade's Chapter 9 example, coz there DAOs are NOT in class diagram but are present in Component and Sequence Diagrams. What do you think?
Ranganathan Kaliyur Mannar wrote:oh ok. I think that sounds reasonable.
In my case, I think the Domain Model is actually simple and doesn't accomodate all the use case requests. So, I have to and its becoming complex - though, I have tried to keep it close to the original as possible.
Thanks for your reply!