| Revision as of 00:42, 16 February 2015 edit187.106.207.242 (talk) →See also← Previous edit | Revision as of 07:47, 12 June 2015 edit undo88.20.72.212 (talk)No edit summaryNext edit → | ||
| Line 5: | Line 5: | ||
| 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. | ||
| Composite applications often incorporate ] 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, ] is a ] standard for composite applications.<ref></ref> | Composite applications often incorporate ] 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 ], ] is a ] standard for composite applications.<ref></ref> | ||
| ==See also== | ==See also== | ||
Revision as of 07:47, 12 June 2015
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
- Web 2.0
- Composite Application Service Assembly (CASA)
- Enterprise service bus (ESB)
- Service-oriented architecture (SOA)
- Service component architecture (SCA)
- Mashup (web application hybrid)
External links
- IBM DeveloperWorks Composite Application Blog
- Composite application guidance from patterns & practices
- NetBeans SOA Composite Application Project Home
- camelse
- Running Apache Camel in OpenESB
- eclipse sirius - Free and GPL eclipse tool to build your own arbitrary complex military grade modeling tools on one hour
- eclipse SCA Tools - Gnu free composite tool
- Free GPL obeodesigner made with eclipse sirius
References
 | This software-engineering-related article is a stub. You can help Misplaced Pages by expanding it. |