Misplaced Pages

Composite application: Difference between revisions

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editNext edit →Content deleted Content addedVisualWikitext
Revision as of 07:47, 12 June 2015 edit88.20.72.212 (talk)No edit summary← Previous edit Revision as of 18:25, 16 April 2016 edit undoDexbot (talk | contribs)Bots192,579 editsm Bot: Cleaning up old interwiki linksNext edit →
Line 33: Line 33:


{{Software-eng-stub}} {{Software-eng-stub}}

]

Revision as of 18:25, 16 April 2016

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

External links

References

  1. OASIS Web Services Composite Application Framework (WS-CAF) TC


Stub icon

This software-engineering-related article is a stub. You can help Misplaced Pages by expanding it.

Categories: