• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Junilu Lacar
  • Liutauras Vilda
Sheriffs:
  • Paul Clapham
  • Jeanne Boyarsky
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Piet Souris
  • Carey Brown
Bartenders:
  • Jesse Duncan
  • Frits Walraven
  • Mikalai Zaikin

JMS Design questions

 
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello,

Please could you help me with the answers to these JMS questions -
1) Scenario
You are required to architect an auction site. Auction item information needs to be delivered in a one-to-many fashion to potential bidders. Biding on auction items must be sent back directly to the broadcaster for the auction item.
Referring to the scenario above, what type of messaging system do you architect?
Choice 1 Publish-and-subscribe (asynchronous) for sending auction-item info and publish-and-subscribe (synchronous) for receiving bids
Choice 2 Publish-and-subscribe for sending auction-item info and point-to-point for bids
Choice 3 Publish-and-subscribe for sending auction-item info and receiving bids
Choice 4 Point-to-point (asynchronous) for sending auction-item info and receiving bids
Choice 5 Point-to-point for sending auction-item info and publish-and-subscribe for bids

I think choice 2 should be the right answer?

2) You are required to architect a distributed Web Services application to perform sophisticated analysis of stock pricing patterns over several years based on parameters passed to your application. To better perform load balancing, your application must be designed to run in a distributed fashion on multiple Linux servers. Note: The number of Linux servers currently available will vary and there can be no modifications to the messaging system as servers come and go.
Referring to the text above, what is the appropriate JMS messaging model for distributing Web Services requests across multiple Web Services applications?
Choice 1 Publish-and-subscribe with consumers subscribed to their own topic
Choice 2 Publish-and-subscribe with multiple consumers subscribed to the same topic
Choice 3 Point-to-point with a queue for each receiver
Choice 4 Peer to peer
Choice 5 Point-to-point with multiple receivers on the same queue

I think Choice 2 should be the right answer?
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic