| Revision as of 18:52, 19 June 2014 editBhny (talk | contribs)14,433 edits →top: WP:REFERS eek!← Previous edit | Revision as of 02:57, 12 October 2014 edit undoChris the speller (talk | contribs)Autopatrolled, Extended confirmed users, Pending changes reviewers867,387 editsm per WP:HYPHEN, sub-subsection 3, points 3,4,5, replaced: service oriented → service-oriented using AWBNext edit → | ||
| Line 1: | Line 1: | ||
| In ], a '''composite application''' is a software application built by combining multiple existing functions into a new application. The technical concept can be compared to ]. However, composite applications use business sources (e.g., existing modules or even ] ) of information, while mashups usually rely on web-based, and often free, sources. | In ], a '''composite application''' is a software application built by combining multiple existing functions into a new application. The technical concept can be compared to ]. However, composite applications use business sources (e.g., existing modules or even ] ) 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 |
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. | 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. | ||
Revision as of 02:57, 12 October 2014
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. |