CSC/ECE 517 Fall 2009/wiki2 17 f1: Difference between revisions

From Expertiza_Wiki
Jump to navigation Jump to search
Line 2: Line 2:


== Service Oriented Architectures==
== Service Oriented Architectures==
[http://en.wikipedia.org/wiki/Service_Oriented_Architectures Service Oriented Architecture] is an approach to building software as a set of autonomous, reusable and [http://en.wikipedia.org/wiki/Interoperability interoperable] units of functionality using open standards. Rather than defining an [http://en.wikipedia.org/wiki/API API], SOA defines the interface in terms of protocols and functionality.
[http://en.wikipedia.org/wiki/Service_Oriented_Architectures Service Oriented Architecture] is a paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains. It provides a uniform means to offer, discover, interact with and use capabilities to produce desired effects consistent with measurable preconditions and expectations.
 
This makes it easier for software integration of different modules developed by different people. Rather than defining an [http://en.wikipedia.org/wiki/API API], SOA defines the interface in terms of protocols and functionality such that modules following these protocols can easily be integrated together. The main characteristics of SOA are:
 
* Based on open standards - The governing principles are free for all to use and not protected by intellectual property.
* Interoperable -
* Autonomous
* Reusable
* Reliable
* Discoverable
* Loosely-Coupled
* Stateless
* Composable
* Manageable
* Secure

Revision as of 20:11, 8 October 2009

Using Reflection and Meta programming to support Service Oriented Architectures

Service Oriented Architectures

Service Oriented Architecture is a paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains. It provides a uniform means to offer, discover, interact with and use capabilities to produce desired effects consistent with measurable preconditions and expectations.

This makes it easier for software integration of different modules developed by different people. Rather than defining an API, SOA defines the interface in terms of protocols and functionality such that modules following these protocols can easily be integrated together. The main characteristics of SOA are:

  • Based on open standards - The governing principles are free for all to use and not protected by intellectual property.
  • Interoperable -
  • Autonomous
  • Reusable
  • Reliable
  • Discoverable
  • Loosely-Coupled
  • Stateless
  • Composable
  • Manageable
  • Secure
Retrieved from "https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2009/wiki2_17_f1&oldid=23071"