Re: [service-orientated-architecture] SOA and ESBs
- In the presentation I gave at Catalyst two weeks ago, I spoke to this. Step one is to understand the capabilities you need in the middle. Now the question is how to achieve these capabilities. If your enterprise has lots of proprietary integration needs, you are likely going to need a developer-focused tool in the middle, such as an ESB. If your enterprise if focused on standards based integration, where the "wiring" is largely a configuration effort by operations, an XML Gateway or Web Service Broker/Intermediary will likely meet your needs.I don't think it's a matter of internal integration versus external integration.-tbOn Jun 27, 2006, at 1:14 AM, Dennis Sosnoski wrote:
> If you are developing applications that are to be deployed on aOk, the assumtion is the "foresee" word.
> Windows platform, and you don't foresee a need to port them to other
> platforms, then .NET is certainly a viable platform.
> As I said in my original response to Dennis, as soon as you implementWithin reason.
> and deploy a solution, you've locked yourself into that platform --
> whether it's IBM WebSphere, BEA WebLogic, JBoss JEMS, Sonic ESB,
> webMethods Fabric, Sun SeeBeyond, Apache Axis, Spring, Struts,
> Hibernate, or whatever. If you think that developing with Java somehow
> gives you vendor and/or framework independence, you're deluding
If the J2EE interfaces are exclusively used then I would argue that the
lock in story is not appropriate.
Using any non-public specification will create a lock in scenario.
I've worked on my projects that used JBoss in the dev & test environments. Then deployed into production on WebSphere.
I also had a project that used JBoss for dev & test and built the application to run
in production on WebSphere & WebLogic.
> .NET is a comprehensive, easy-to-use, development framework -- farNot wanting to open a can of worms or debate the point.
> easier than any Java-based counterpart. And it's certainly better
> optimized for the Windows platform than any Java framework. It
> performs better, and except for the most extreme cases, supports
> comparable scalability. Why wouldn't it be viable?
Yes .NET can be used as can any other technology.
Just wanted to get an insight into your mind set on .NET.
Thanks for your comments.
360°: Your own space to share what you want with who you want!