Thought I’d start up a purely academic and hypothetical discussion around using IS for something it was not intended for–hosting “business logic.”
I’d venture to say that the majority of the wMUsers participants are quite familiar with n-tier application architecture idea. An application might have these conceptual layers:
There are many, many tools available to implement such an application. J2EE, .Net, etc. WebLogic and WebSphere are clear market leaders in the J2EE app server space.
The focus of my hypothetical is on the business logic tier. Business logic is typically implemented using beans, EJBs, C++. C#, .Net assemblies, and so on.
What would be the implications, pros and cons of designing and implementing the business logic using Integration Server? And I don’t mean exposing business logic hosted somewhere else. I mean really implementing the “guts” of an application in IS.
Some immediate “no ways” come to mind for me but there are also some “could be cools” also. Particularly when the communication between the layers would be web services.