The question is "Will SOA kill the idea of Applications?". I think it won't but I think SOA will well impact the granularity of applications. Here an extract of a recent blog "SOA, the end of applications <http://blogs.ittoolbox.com/eai/applications/archives/soa-the-end-of-app\ lications-12994> " about this:
<< From a user perspective, the application is that icon on the desktop or this link in my bookmarks. From an Enterprise architecture viewpoint, an application is more than that, it is also this logical box that is managing that data and implements the necessary business logic to support different services or processes. So if you look at applications from the user perspective, indeed, the future looks like applications will be composite, what will be shown on one single screen will be the aggregation of information potentially coming from various sources and the user actions will trigger a process potentially expanding through several systems. Kind of application portals. But the reality is that the back-end applications will still be there. I think back-end applications will be long-term influenced by SOA as well. As the cost of interoperability is expected to be lower, there is no reason to continue building large and complex proprietary systems. The size of the building blocks will start to decrease and more often, we will plan for the replacement of a block instead of its upgrade.>> Robin --- In [email protected], Stefan Tilkov <[EMAIL PROTECTED]> wrote: > > On Nov 23, 2006, at 4:01 AM, Todd Biske wrote: > > > Your architecture may be SOA-compatible if the term application has > > been removed from your company's lexicon. > > I think I agree with your basic point - you should be developing, > deploying, versioning, managing, buying, outsourcing services, not > applications. But in the end, something has to actually *use* all > those services. That's still an "application" in my vocabulary. > > Stefan > -- > Stefan Tilkov, http://www.innoq.com/blog/st/ >
