-
1. Re: SOA Architecture Design
marklittle Aug 29, 2008 12:14 PM (in response to jerry_tom)Hmmm, lots of questions here and lots of possible answers. I suppose the first question I would have is: have you downloaded the ESB and gone through the documentation? That's always a good starting point, followed by the quickstarts. Then it would probably make sense to have a separate discussion item for each question you want to raise. Makes sense?
-
2. Re: SOA Architecture Design
jerry_tom Aug 30, 2008 3:24 AM (in response to jerry_tom)Thanks for the input.
Actually I did not download the ESB, but I did read the JSR 208/312 specification which is what ESB.
Well before I could download and understand in the coding internals,I would like to decide if I should go for ESB or no ESB, what is the advantange I would gain and what is the time going to be involved, plus how stable is it.
Also from High availablity point of view,what is the reality.
Please provide your inputs, I need to decide what my SOA should be comprised off. -
3. Re: SOA Architecture Design
marklittle Sep 2, 2008 10:38 AM (in response to jerry_tom)The debate about ESBs and how they relate to SOA is often as difficult as the REST versus WS-* debates that rage elsewhere. It's obviously hard to expect an objective answer from a company that provides an ESB, but I would say that a good ESB can be the basis of a Service Oriented Infrastructure. JBossESB falls into that category IMO (but again, you'd have to decide whether or not I'm being objective).
The ESB should give you the tools and infrastructure to develop an SOA-based application without tying yourself to an underlying technology platform (well, of course you'll be tied to the ESB since standards in this area are still lacking). So for example, you shouldn't have to go with WS-* if that's not what you need: FTP based interactions may be more valid in your environment. A good ESB should help you make the right choices and not force you into them. JBossESB supports more than just WS-*, in case you hadn't noticed.
As for high availability: you should definitely take a look at our wiki and documentation. We support HA based services in a number of ways. Once again, you're not tied to a specific implementation.
I would definitely recommend that you check out our project documentation (available on the labs page as well as what comes with the ESB binary). It should help you to fill in some of the blanks. Maybe then you'll have some specific questions about our ESB and we'd be happy to help answer them. -
4. Re: SOA Architecture Design
jerry_tom Sep 7, 2008 10:24 AM (in response to jerry_tom)Thank you very much for the inputs and directions provided, might be I need to spend more time and organize my thoughts for my specific problem scope.
I will go back and do more home work and come back for any help.
Appreciate your support.