| Revision as of 12:32, 23 February 2011 edit115.252.135.88 (talk)No edit summaryTag: references removed← Previous edit | Revision as of 12:32, 23 February 2011 edit undoClueBot NG (talk | contribs)Bots, Pending changes reviewers, Rollbackers6,438,502 editsm Reverting possible vandalism by 115.252.135.88 to version by Glennblock. False positive? Report it. Thanks, ClueBot NG. (301832) (Bot)Next edit → | ||
| Line 1: | Line 1: | ||
| In ], the term '''composite application''' expresses a perspective of software engineering that defines an 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. | |||
| composite applications means mainly different Application are working independentialy and combinning the those are all a single unit is called composite Application so this is called as a loosely coupled management system. | |||
| this our thgought | |||
| 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. | |||
| Thanks of review give me the comment | |||
| 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>. | |||
| ==See also== | |||
| *] | |||
| *] | |||
| *] | |||
| * ] | |||
| ==External links== | |||
| * Research paper (PDF). | |||
| * White Paper (PDF). | |||
| * | |||
| * Gartner | |||
| * | |||
| ==References== | |||
| <references/> | |||
| {{Software-eng-stub}} | |||
| ] | |||
| ] | |||
| ] | |||
Revision as of 12:32, 23 February 2011
In computing, the term composite application expresses a perspective of software engineering that defines an 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
- On Estimating the Security Risks of Composite Software Services Research paper (PDF).
- Visual Composite Applications: Magnifying Data Return on Investment (ROI) White Paper (PDF).
- IBM DeveloperWorks Composite Application Blog
- Magic Quadrant for Application Infrastructure for SOA Composite Application Projects Gartner
- Composite application guidance from patterns & practices
References
 | This software-engineering-related article is a stub. You can help Misplaced Pages by expanding it. |