View Single Post
  #2 (permalink)  
Old July 2nd, 2007, 23:12
chrisplough's Avatar
chrisplough chrisplough is offline
Site Moderator
 
Join Date: Jun 2006
Location: West Chester, PA
Posts: 864
Blog Entries: 7
Groans: 0
Groaned at 1 Time in 1 Post
Thanks: 55
Thanked 213 Times in 126 Posts
Rep Power: 10
chrisplough has a spectacular aura aboutchrisplough has a spectacular aura aboutchrisplough has a spectacular aura about
Send a message via AIM to chrisplough
Re: Protocol for Integration - HTTP/QUEUE/WEB SERVICE

Hello!

At a high level, here's my thoughts:

HTTP:
  • Easy to implement
  • Lightweight
  • Compatible with most integration engines
  • Very little error correction
  • Simple / Simplistic (depends on your point of view)
OAQ:
  • Integrates directly with DB - bypasses web/app server
  • Complex
  • Have seen performance issues in production, though I'm not sure if that was OAQ or the configuration
BPEL:
  • New, interesting technology
  • Very capable language for handling scenarios
  • Integration engines are not as mature (Oracle, Active Endpoints)
Web Services:
  • New, interesting technology
  • The direction integration seems to be going
  • A great keyword for the resume :P
  • Complex to configure
  • Only available with OTM on WebLogic (currently)
Let me know your thoughts and we can go into greater detail.

Thanks!
--Chris
__________________
Chris Plough
MavenWire

www.MavenWire.com