This is an old revision of this page, as edited by Bhny (talk | contribs) at 18:52, 19 June 2014 (→top: WP:REFERS eek!). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
Revision as of 18:52, 19 June 2014 by Bhny (talk | contribs) (→top: WP:REFERS eek!)(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)In computing, a composite application is a software application built by combining multiple existing functions into a new application. The technical concept can be compared to mashups. However, composite applications use business sources (e.g., existing modules or even Web services ) of information, while mashups usually rely on web-based, and often free, sources.
It is wrong to assume that composite applications are by definition part of a service oriented architecture (SOA). Composite applications can be built using any technology or architecture.
A composite application consists of functionality drawn from several different sources. The components may be individual selected functions from within other applications, or entire systems whose outputs have been packaged as business functions, modules, or web services.
Composite applications often incorporate orchestration of "local" application logic to control how the composed functions interact with each other to produce the new, derived functionality. For composite applications that are based on SOA, WS-CAF is a Web services standard for composite applications.
See also
- Service-oriented architecture
- Web 2.0
- Service component architecture
- Mashup (web application hybrid)
External links
- IBM DeveloperWorks Composite Application Blog
- Composite application guidance from patterns & practices
References
 | This software-engineering-related article is a stub. You can help Misplaced Pages by expanding it. |