Can I assume that by "ESB" you are referring to a comprehensive SOA infrastructure, and not to an ESB products? (A comprehensive SOA infrastructure comprises multiple service platforms, multiple mediation systems, multiple management systems, and one or more registries. There's no way that an ESB product can provide a complete SOA infrastructure.) My recommendation is that you not attempt to overload the ESB term this way, because it will no doubt generate confusion among your readers.

btw -- in my most recent report, I spent 65 pages just discussing SOA infrastructure. I think your goal to say all there is to say about SOA in 60-70 pages is challenging, to say the least.

Anne

On 2/17/06, Andrei Postolache <[EMAIL PROTECTED]> wrote:
Hi,

I'm working on a mini book on SOA for the InfoQ Enterprise Development Community. This mini book is aimed mainly at the technical architect and wants to be the definitive (but succinct) "document" on SOA. It has to cover, in 60-70 pages, all that has to be covered about SOA.

What I have attached is a TOC with some explanations inside. Any feedback is highly appreciated. Let me know if I'm not focusing on the right things, if I'm missing something etc. Any advice will be of great help.

Thanks,
Andrei


SPONSORED LINKS
Computer software Computer aided design software Computer job
Soa Service-oriented architecture


YAHOO! GROUPS LINKS







SPONSORED LINKS
Computer software Computer aided design software Computer job
Soa Service-oriented architecture


YAHOO! GROUPS LINKS




Reply via email to