<< back to glossary · Version History · Comments

Service Oriented Architecture

This refers to a technique for designing complex applications where key elements of the functionality are separated into modules (or 'services'). These are semi-independent from the core system and can potentially be called by other applications in a client/server model. The biggest single benefit of SOA is scalability. Since the service is independent of the main application it can be scaled up to support increased demand without any specific modifications being required. It also eases functional enhancements since one service can be replaced by another far more easily.

In Digital Asset Management systems, it is common to have dedicated services for a variety of intensive features, in particular asset manipulation and processing, but also searching, indexing, metadata importing/exporting, business intelligence and a range of specialist requirements like zipping big collections of files. SOA is also beneficial for application integration since third party systems can use features on a selective basis and connect into them in the same fashion as the central DAM system.

Rating: 0/5 (0 votes cast)

Version History for Service Oriented Architecture

Click version numbers to view differences.

Current Version (3)
Edited by Ralph Windsor on 17/06/2020 at 16:59

Version 2
Edited by Ralph Windsor on 17/06/2020 at 16:59

Version 1
Created by Ralph Windsor on 03/06/2014 at 10:04

Comments for Service Oriented Architecture

There are currently no comments for this term.

Post a Comment

You must be registered and logged in to post a comment.