1 Reply Latest reply on Sep 21, 2007 12:59 AM by genman

    Benefits of using JBoss product suite for distributed system

    scrut

      As I am starting a new project, I am wondering what the benefits of using JBoss products are as supposed to something like Tomcat + Axis + Torque + POJO.

      As you can see in the following images, I am about to build a distributed system with one job manager and several job handlers. Each node may be on a different server.
      The job manager has a web interface where a user can enter a command which is then passed to one of the n job handlers via SOAP message.
      The job handler then reads mails, web sites and other documents (which may take up to several hours).
      Once the job is completed, the job handler contacts the job dispatcher and submits the results of the performed queries.
      That's all. No heavy duty DB stuff, just distributed data processing.
      DBMS are only for log files and such.

      What does JBoss provide for developing this?
      What are the advantages of a JBoss based approach rather than Tomcat/Axis/WAR?

      Thanks a lot!

      Overview of my project:
      [img]http://www.cmklein.de/Overview.gif[/img]

      Details of my project:
      [img]http://www.cmklein.de/Details.gif[/img]

        • 1. Re: Benefits of using JBoss product suite for distributed sy
          genman

          When I think of distributed jobs, I think of JMS and MDB.

          Rather than using SOAP internally, simply publish a JMS message to the cluster. Since JMS messages are processed asynchronously, unlike SOAP, your SOAP client doesn't need to block for completion.

          JMS has a notion of transactions and supports things such as automatic retries. So, if the system goes down, your jobs aren't lost.