Service-oriented programming - Revision history

Tc14Hd: Added short description

2024-09-11T15:49:56Z

Added short description

← Previous revision		Revision as of 15:49, 11 September 2024
Line 1:		Line 1:
			{{Short description\|Programming paradigm}}
	{{Ref improve\|date=February 2024}}		{{Ref improve\|date=February 2024}}
	'''Service-oriented programming''' (SOP) is a [[programming paradigm]] that uses "services" as the unit of computer work, to design and implement integrated business applications and [[mission critical]] software programs. Services can represent steps of [[business process]]es and thus one of the main applications of this paradigm is the cost-effective delivery of standalone or composite business applications that can "integrate from the inside-out". It inherently promotes [[service-oriented architecture]] (SOA), however, it is not the same as SOA. While SOA focuses on communication between systems using "services",<ref>{{cite journal \| last=Laskey \| first=Kathryn B. \| last2=Laskey \| first2=Kenneth \| title=Service oriented architecture \| journal=WIREs Computational Statistics \| volume=1 \| issue=1 \|year=2009\| doi=10.1002/wics.8 \| page=101}}</ref> SOP provides a new technique to build agile application [[memory module\|modules]] using in-memory services as the unit of work.		'''Service-oriented programming''' (SOP) is a [[programming paradigm]] that uses "services" as the unit of computer work, to design and implement integrated business applications and [[mission critical]] software programs. Services can represent steps of [[business process]]es and thus one of the main applications of this paradigm is the cost-effective delivery of standalone or composite business applications that can "integrate from the inside-out". It inherently promotes [[service-oriented architecture]] (SOA), however, it is not the same as SOA. While SOA focuses on communication between systems using "services",<ref>{{cite journal \| last=Laskey \| first=Kathryn B. \| last2=Laskey \| first2=Kenneth \| title=Service oriented architecture \| journal=WIREs Computational Statistics \| volume=1 \| issue=1 \|year=2009\| doi=10.1002/wics.8 \| page=101}}</ref> SOP provides a new technique to build agile application [[memory module\|modules]] using in-memory services as the unit of work.

MrOllie: Restored revision 1204521715 by Egeymi (talk): Unsourced opinion

2024-07-01T11:11:18Z

Restored revision 1204521715 by Egeymi (talk): Unsourced opinion

← Previous revision		Revision as of 11:11, 1 July 2024
Line 101:		Line 101:
	* Application [[Application virtualization\|Virtualization]]: SOP promotes built-in micro control over location transparency of the service constituents of any service module. This results in automatic and granular [[Application virtualization\|virtualization]] of application components (versus an entire application process) across a [[cluster (computing)\|cluster]] or [[grid computing\|grid]] of SOP runtime platforms.		* Application [[Application virtualization\|Virtualization]]: SOP promotes built-in micro control over location transparency of the service constituents of any service module. This results in automatic and granular [[Application virtualization\|virtualization]] of application components (versus an entire application process) across a [[cluster (computing)\|cluster]] or [[grid computing\|grid]] of SOP runtime platforms.
	* [[Service-oriented architecture]] (SOA) and demand for integrated and composite applications: in the beginning, the adoption of SOP will follow the adoption curve of SOA with a small lag. This is because services generated through SOA can be easily assembled and consumed through SOP. The more Web services proliferate, the more it makes sense to take advantage of the semantic nature of SOP. On the other hand, since SOA is inherent in SOP, SOP provides a cost-effective way to deliver SOA to mainstream markets.		* [[Service-oriented architecture]] (SOA) and demand for integrated and composite applications: in the beginning, the adoption of SOP will follow the adoption curve of SOA with a small lag. This is because services generated through SOA can be easily assembled and consumed through SOP. The more Web services proliferate, the more it makes sense to take advantage of the semantic nature of SOP. On the other hand, since SOA is inherent in SOP, SOP provides a cost-effective way to deliver SOA to mainstream markets.
	* [[Software as a service]] (SaaS): capabilities of the current SaaS platforms cannot address the customization and integration complexities required by large enterprises. SOP can significantly reduce the complexity of integration and customization. This will drive SOP into the next generation SaaS platforms. This advancement will not only meet the specific needs of large enterprises but also drive innovation, efficiency, and reliability in the next generation of SaaS platforms. Consequently, SOPs will play a critical role in transforming SaaS offerings, making them more adaptable and capable of supporting diverse and complex business environments.		* [[Software as a service]] (SaaS): capabilities of the current SaaS platforms cannot address the customization and integration complexities required by large enterprises. SOP can significantly reduce the complexity of integration and customization. This will drive SOP into the next generation SaaS platforms.

	== See also ==		== See also ==

A.Deyna: The source Laskey, Kathryn B.; Laskey, Kenneth (2009). "Service oriented architecture" provides a more extensive explanation of how Saas relates to sop, which is important for understanding

2024-07-01T10:28:21Z

The source Laskey, Kathryn B.; Laskey, Kenneth (2009). "Service oriented architecture" provides a more extensive explanation of how Saas relates to sop, which is important for understanding

← Previous revision		Revision as of 10:28, 1 July 2024
Line 101:		Line 101:
	* Application [[Application virtualization\|Virtualization]]: SOP promotes built-in micro control over location transparency of the service constituents of any service module. This results in automatic and granular [[Application virtualization\|virtualization]] of application components (versus an entire application process) across a [[cluster (computing)\|cluster]] or [[grid computing\|grid]] of SOP runtime platforms.		* Application [[Application virtualization\|Virtualization]]: SOP promotes built-in micro control over location transparency of the service constituents of any service module. This results in automatic and granular [[Application virtualization\|virtualization]] of application components (versus an entire application process) across a [[cluster (computing)\|cluster]] or [[grid computing\|grid]] of SOP runtime platforms.
	* [[Service-oriented architecture]] (SOA) and demand for integrated and composite applications: in the beginning, the adoption of SOP will follow the adoption curve of SOA with a small lag. This is because services generated through SOA can be easily assembled and consumed through SOP. The more Web services proliferate, the more it makes sense to take advantage of the semantic nature of SOP. On the other hand, since SOA is inherent in SOP, SOP provides a cost-effective way to deliver SOA to mainstream markets.		* [[Service-oriented architecture]] (SOA) and demand for integrated and composite applications: in the beginning, the adoption of SOP will follow the adoption curve of SOA with a small lag. This is because services generated through SOA can be easily assembled and consumed through SOP. The more Web services proliferate, the more it makes sense to take advantage of the semantic nature of SOP. On the other hand, since SOA is inherent in SOP, SOP provides a cost-effective way to deliver SOA to mainstream markets.
	* [[Software as a service]] (SaaS): capabilities of the current SaaS platforms cannot address the customization and integration complexities required by large enterprises. SOP can significantly reduce the complexity of integration and customization. This will drive SOP into the next generation SaaS platforms.		* [[Software as a service]] (SaaS): capabilities of the current SaaS platforms cannot address the customization and integration complexities required by large enterprises. SOP can significantly reduce the complexity of integration and customization. This will drive SOP into the next generation SaaS platforms. This advancement will not only meet the specific needs of large enterprises but also drive innovation, efficiency, and reliability in the next generation of SaaS platforms. Consequently, SOPs will play a critical role in transforming SaaS offerings, making them more adaptable and capable of supporting diverse and complex business environments.

	== See also ==		== See also ==

Egeymi: + source WP:FEB24; expanded els; removed one promotional and one dead link

2024-02-07T08:02:15Z

+ source WP:FEB24; expanded els; removed one promotional and one dead link

← Previous revision		Revision as of 08:02, 7 February 2024
Line 1:		Line 1:
	{{~~Unreferenced~~\|date=February ~~2008~~}}		{{Ref improve\|date=February 2024}}
	'''Service-oriented programming''' (SOP) is a [[programming paradigm]] that uses "services" as the unit of computer work, to design and implement integrated business applications and [[mission critical]] software programs. Services can represent steps of [[business process]]es and thus one of the main applications of this paradigm is the cost-effective delivery of standalone or composite business applications that can "integrate from the inside-out". It inherently promotes [[service-oriented architecture]] (SOA), however, it is not the same as SOA. While SOA focuses on communication between systems using "services", SOP provides a new technique to build agile application [[memory module\|modules]] using in-memory services as the unit of work.		'''Service-oriented programming''' (SOP) is a [[programming paradigm]] that uses "services" as the unit of computer work, to design and implement integrated business applications and [[mission critical]] software programs. Services can represent steps of [[business process]]es and thus one of the main applications of this paradigm is the cost-effective delivery of standalone or composite business applications that can "integrate from the inside-out". It inherently promotes [[service-oriented architecture]] (SOA), however, it is not the same as SOA. While SOA focuses on communication between systems using "services",<ref>{{cite journal \| last=Laskey \| first=Kathryn B. \| last2=Laskey \| first2=Kenneth \| title=Service oriented architecture \| journal=WIREs Computational Statistics \| volume=1 \| issue=1 \|year=2009\| doi=10.1002/wics.8 \| page=101}}</ref> SOP provides a new technique to build agile application [[memory module\|modules]] using in-memory services as the unit of work.

	An in-memory service in SOP can be transparently externalized as a [[web service]] operation. Due to language and platform independent Web Service standards, SOP embraces all existing programming paradigms, languages and platforms. In SOP, the design of the programs pivot around the [[semantics]] of service calls, logical routing and data flow description across well-defined service interfaces. All SOP program modules are encapsulated as services and a service can be composed of other nested services in a hierarchical manner with virtually limitless depth to this service stack hierarchy. A composite service can also contain programming constructs some of which are specific and unique to SOP. A service can be an externalized system component that is accessed via any proprietary API or web service standards utilizing an in-memory plug-in technique.		An in-memory service in SOP can be transparently externalized as a [[web service]] operation. Due to language and platform independent Web Service standards, SOP embraces all existing programming paradigms, languages and platforms. In SOP, the design of the programs pivot around the [[semantics]] of service calls, logical routing and data flow description across well-defined service interfaces. All SOP program modules are encapsulated as services and a service can be composed of other nested services in a hierarchical manner with virtually limitless depth to this service stack hierarchy. A composite service can also contain programming constructs some of which are specific and unique to SOP. A service can be an externalized system component that is accessed via any proprietary API or web service standards utilizing an in-memory plug-in technique.
Line 105:		Line 105:
	== See also ==		== See also ==
	* [[Microservices]]		* [[Microservices]]

			==References==
			{{Reflist}}

	==External links==		==External links==
		⚫	* [https://doi.org/10.1007%2F3-540-46020-9_19 Service-Oriented Programming: A New Paradigm of Software Reuse]
	* http://nextaxiom.com
		⚫	* [https://web.archive.org/web/20090505205415/http://blog.itaniumsolutions.org/2008/01/ Grid Virtualization and Itanium®-based Solutions]
⚫	* [https://doi.org/10.1007%2F3-540-46020-9_19 ~~DOI.org] "~~Service-Oriented Programming: A New Paradigm of Software Reuse"
⚫	* https://web.archive.org/web/20090505205415/http://blog.itaniumsolutions.org/2008/01/
	* http://in.sys-con.com/node/467329

	[[Category:Service-oriented (business computing)]]		[[Category:Service-oriented (business computing)]]

Joy: use the whole term for the link, disambiguating it

2023-04-22T13:36:45Z

use the whole term for the link, disambiguating it

← Previous revision		Revision as of 13:36, 22 April 2023
Line 85:		Line 85:

	===Consumer account provisioning===		===Consumer account provisioning===
	Select services can be deployed securely for external programmatic consumption by a presentation ([[Graphical user interface\|GUI]]) layer, or other applications. Once service accounts are defined, the SOP runtime environment automatically manages access through consumer ~~account~~ [[provisioning]] mechanisms.		Select services can be deployed securely for external programmatic consumption by a presentation ([[Graphical user interface\|GUI]]) layer, or other applications. Once service accounts are defined, the SOP runtime environment automatically manages access through consumer [[account provisioning]] mechanisms.

	===Security===		===Security===

Elias Niklas at 08:12, 10 April 2023

2023-04-10T08:12:49Z

← Previous revision		Revision as of 08:12, 10 April 2023
Line 2:		Line 2:
	'''Service-oriented programming''' (SOP) is a [[programming paradigm]] that uses "services" as the unit of computer work, to design and implement integrated business applications and [[mission critical]] software programs. Services can represent steps of [[business process]]es and thus one of the main applications of this paradigm is the cost-effective delivery of standalone or composite business applications that can "integrate from the inside-out". It inherently promotes [[service-oriented architecture]] (SOA), however, it is not the same as SOA. While SOA focuses on communication between systems using "services", SOP provides a new technique to build agile application [[memory module\|modules]] using in-memory services as the unit of work.		'''Service-oriented programming''' (SOP) is a [[programming paradigm]] that uses "services" as the unit of computer work, to design and implement integrated business applications and [[mission critical]] software programs. Services can represent steps of [[business process]]es and thus one of the main applications of this paradigm is the cost-effective delivery of standalone or composite business applications that can "integrate from the inside-out". It inherently promotes [[service-oriented architecture]] (SOA), however, it is not the same as SOA. While SOA focuses on communication between systems using "services", SOP provides a new technique to build agile application [[memory module\|modules]] using in-memory services as the unit of work.

	An in-memory service in SOP can be transparently externalized as a [[web service]] operation. Due to language and platform independent Web Service standards, SOP embraces all existing programming paradigms, languages and platforms. In SOP, the design of the programs pivot around the [[semantics]] of service calls, logical routing and data flow description across well-defined service interfaces. All SOP program modules are encapsulated as services and a service can be composed of other nested services in a hierarchical manner with virtually limitless depth to this service stack hierarchy. A composite service can also contain programming constructs some of which are specific and unique to SOP. A service can be an externalized component ~~from~~ ~~another system~~ accessed ~~either~~ ~~through~~ ~~using~~ web service standards ~~or any proprietary API through~~ an in-memory plug-in ~~mechanism~~.		An in-memory service in SOP can be transparently externalized as a [[web service]] operation. Due to language and platform independent Web Service standards, SOP embraces all existing programming paradigms, languages and platforms. In SOP, the design of the programs pivot around the [[semantics]] of service calls, logical routing and data flow description across well-defined service interfaces. All SOP program modules are encapsulated as services and a service can be composed of other nested services in a hierarchical manner with virtually limitless depth to this service stack hierarchy. A composite service can also contain programming constructs some of which are specific and unique to SOP. A service can be an externalized system component that is accessed via any proprietary API or web service standards utilizing an in-memory plug-in technique.

	While SOP supports the basic [[programming language\|programming]] constructs for sequencing, selection and iteration, it is differentiated with a slew of new programming constructs that provide built-in native ability geared towards data list manipulation, [[data integration]], automated [[Thread (computer science)\|multithreading]] of service modules, declarative context management and [[synchronization]] of services. SOP design enables programmers to semantically synchronize the execution of services in order to guarantee that it is correct, or to declare a service module as a transaction boundary with automated commit/rollback behavior.		While SOP supports the basic [[programming language\|programming]] constructs for sequencing, selection and iteration, it is differentiated with a slew of new programming constructs that provide built-in native ability geared towards data list manipulation, [[data integration]], automated [[Thread (computer science)\|multithreading]] of service modules, declarative context management and [[synchronization]] of services. SOP design enables programmers to semantically synchronize the execution of services in order to guarantee that it is correct, or to declare a service module as a transaction boundary with automated commit/rollback behavior.

RobinHood70: Punctuation; remove unnecessary title

2023-02-20T15:33:26Z

Punctuation; remove unnecessary title

← Previous revision		Revision as of 15:33, 20 February 2023
Line 1:		Line 1:
	{{Unreferenced\|date=February 2008}}		{{Unreferenced\|date=February 2008}}
	'''Service-oriented programming''' (SOP) is a [[programming paradigm]] that uses "services" as the unit of computer work, to design and implement integrated business applications and [[mission critical]] software programs. Services can represent steps of [[business process]]es and thus one of the main applications of this paradigm is the cost-effective delivery of standalone or composite business applications that can "integrate from the inside-out"		'''Service-oriented programming''' (SOP) is a [[programming paradigm]] that uses "services" as the unit of computer work, to design and implement integrated business applications and [[mission critical]] software programs. Services can represent steps of [[business process]]es and thus one of the main applications of this paradigm is the cost-effective delivery of standalone or composite business applications that can "integrate from the inside-out". It inherently promotes [[service-oriented architecture]] (SOA), however, it is not the same as SOA. While SOA focuses on communication between systems using "services", SOP provides a new technique to build agile application [[memory module\|modules]] using in-memory services as the unit of work.

	<nowiki>==Introduction ==</nowiki>

	SOP inherently promotes [[service-oriented architecture]] (SOA), however, it is not the same as SOA. While SOA focuses on communication between systems using "services", SOP provides a new technique to build agile application [[memory module\|modules]] using in-memory services as the unit of work.

	An in-memory service in SOP can be transparently externalized as a [[web service]] operation. Due to language and platform independent Web Service standards, SOP embraces all existing programming paradigms, languages and platforms. In SOP, the design of the programs pivot around the [[semantics]] of service calls, logical routing and data flow description across well-defined service interfaces. All SOP program modules are encapsulated as services and a service can be composed of other nested services in a hierarchical manner with virtually limitless depth to this service stack hierarchy. A composite service can also contain programming constructs some of which are specific and unique to SOP. A service can be an externalized component from another system accessed either through using web service standards or any proprietary API through an in-memory plug-in mechanism.		An in-memory service in SOP can be transparently externalized as a [[web service]] operation. Due to language and platform independent Web Service standards, SOP embraces all existing programming paradigms, languages and platforms. In SOP, the design of the programs pivot around the [[semantics]] of service calls, logical routing and data flow description across well-defined service interfaces. All SOP program modules are encapsulated as services and a service can be composed of other nested services in a hierarchical manner with virtually limitless depth to this service stack hierarchy. A composite service can also contain programming constructs some of which are specific and unique to SOP. A service can be an externalized component from another system accessed either through using web service standards or any proprietary API through an in-memory plug-in mechanism.
Line 14:		Line 10:
	==Fundamental concepts==		==Fundamental concepts==
	SOP concepts provide a robust base for a semantic approach to programming integration and application logic. There are three significant benefits to this approach:		SOP concepts provide a robust base for a semantic approach to programming integration and application logic. There are three significant benefits to this approach:
	* Semantically, it can raise the level of abstraction for creating composite business applications and thus significantly increase responsiveness to change (i.e. [[business agility]])		* Semantically, it can raise the level of abstraction for creating composite business applications and thus significantly increase responsiveness to change (i.e. [[business agility]]).
	* Gives rise to the unification of integration and software component development techniques under a single concept and thus significantly reduces the complexity of integration. This unified approach enables "inside-out integration" without the need to replicate data, therefore, significantly reducing the cost and complexity of the overall explanation		* Gives rise to the unification of integration and software component development techniques under a single concept and thus significantly reduces the complexity of integration. This unified approach enables "inside-out integration" without the need to replicate data, therefore, significantly reducing the cost and complexity of the overall explanation.
	* Automate multi-threading and [[Application virtualization\|virtualization]] of applications at the granular (unit-of-work) level.		* Automate multi-threading and [[Application virtualization\|virtualization]] of applications at the granular (unit-of-work) level.

86.22.148.239 at 10:35, 11 January 2023

2023-01-11T10:35:27Z

← Previous revision		Revision as of 10:35, 11 January 2023
Line 2:		Line 2:
	'''Service-oriented programming''' (SOP) is a [[programming paradigm]] that uses "services" as the unit of computer work, to design and implement integrated business applications and [[mission critical]] software programs. Services can represent steps of [[business process]]es and thus one of the main applications of this paradigm is the cost-effective delivery of standalone or composite business applications that can "integrate from the inside-out"		'''Service-oriented programming''' (SOP) is a [[programming paradigm]] that uses "services" as the unit of computer work, to design and implement integrated business applications and [[mission critical]] software programs. Services can represent steps of [[business process]]es and thus one of the main applications of this paradigm is the cost-effective delivery of standalone or composite business applications that can "integrate from the inside-out"

	==Introduction ==		<nowiki>==Introduction ==</nowiki>

	SOP inherently promotes [[service-oriented architecture]] (SOA), however, it is not the same as SOA. While SOA focuses on communication between systems using "services", SOP provides a new technique to build agile application [[memory module\|modules]] using in-memory services as the unit of work.		SOP inherently promotes [[service-oriented architecture]] (SOA), however, it is not the same as SOA. While SOA focuses on communication between systems using "services", SOP provides a new technique to build agile application [[memory module\|modules]] using in-memory services as the unit of work.

Line 14:		Line 15:
	SOP concepts provide a robust base for a semantic approach to programming integration and application logic. There are three significant benefits to this approach:		SOP concepts provide a robust base for a semantic approach to programming integration and application logic. There are three significant benefits to this approach:
	* Semantically, it can raise the level of abstraction for creating composite business applications and thus significantly increase responsiveness to change (i.e. [[business agility]])		* Semantically, it can raise the level of abstraction for creating composite business applications and thus significantly increase responsiveness to change (i.e. [[business agility]])
	* Gives rise to the unification of integration and software component development techniques under a single concept and thus significantly reduces the complexity of integration. This unified approach enables "inside-out integration" without the need to replicate data, therefore, significantly reducing the cost and complexity of the overall ~~solution~~		* Gives rise to the unification of integration and software component development techniques under a single concept and thus significantly reduces the complexity of integration. This unified approach enables "inside-out integration" without the need to replicate data, therefore, significantly reducing the cost and complexity of the overall explanation
	* Automate multi-threading and [[Application virtualization\|virtualization]] of applications at the granular (unit-of-work) level.		* Automate multi-threading and [[Application virtualization\|virtualization]] of applications at the granular (unit-of-work) level.

GünniX: v2.04 - Fix errors for CW project (Heading ends with a colon)

2021-04-11T17:50:30Z

v2.04 - Fix errors for CW project (Heading ends with a colon)

← Previous revision		Revision as of 17:50, 11 April 2021
Line 106:		Line 106:
	* [[Software as a service]] (SaaS): capabilities of the current SaaS platforms cannot address the customization and integration complexities required by large enterprises. SOP can significantly reduce the complexity of integration and customization. This will drive SOP into the next generation SaaS platforms.		* [[Software as a service]] (SaaS): capabilities of the current SaaS platforms cannot address the customization and integration complexities required by large enterprises. SOP can significantly reduce the complexity of integration and customization. This will drive SOP into the next generation SaaS platforms.

			== See also ==
	== Related subjects of interest: ==

	* [[Microservices]]		* [[Microservices]]

ElloraToronto: Added related subject of interest

2021-01-19T21:14:27Z

Added related subject of interest

← Previous revision		Revision as of 21:14, 19 January 2021
Line 105:		Line 105:
	* [[Service-oriented architecture]] (SOA) and demand for integrated and composite applications: in the beginning, the adoption of SOP will follow the adoption curve of SOA with a small lag. This is because services generated through SOA can be easily assembled and consumed through SOP. The more Web services proliferate, the more it makes sense to take advantage of the semantic nature of SOP. On the other hand, since SOA is inherent in SOP, SOP provides a cost-effective way to deliver SOA to mainstream markets.		* [[Service-oriented architecture]] (SOA) and demand for integrated and composite applications: in the beginning, the adoption of SOP will follow the adoption curve of SOA with a small lag. This is because services generated through SOA can be easily assembled and consumed through SOP. The more Web services proliferate, the more it makes sense to take advantage of the semantic nature of SOP. On the other hand, since SOA is inherent in SOP, SOP provides a cost-effective way to deliver SOA to mainstream markets.
	* [[Software as a service]] (SaaS): capabilities of the current SaaS platforms cannot address the customization and integration complexities required by large enterprises. SOP can significantly reduce the complexity of integration and customization. This will drive SOP into the next generation SaaS platforms.		* [[Software as a service]] (SaaS): capabilities of the current SaaS platforms cannot address the customization and integration complexities required by large enterprises. SOP can significantly reduce the complexity of integration and customization. This will drive SOP into the next generation SaaS platforms.

			== Related subjects of interest: ==

			* [[Microservices]]

	==External links==		==External links==

← Previous revision		Revision as of 15:49, 11 September 2024
Line 1:		Line 1:
			{{Short description\|Programming paradigm}}
	{{Ref improve\|date=February 2024}}		{{Ref improve\|date=February 2024}}
	'''Service-oriented programming''' (SOP) is a [[programming paradigm]] that uses "services" as the unit of computer work, to design and implement integrated business applications and [[mission critical]] software programs. Services can represent steps of [[business process]]es and thus one of the main applications of this paradigm is the cost-effective delivery of standalone or composite business applications that can "integrate from the inside-out". It inherently promotes [[service-oriented architecture]] (SOA), however, it is not the same as SOA. While SOA focuses on communication between systems using "services",<ref>{{cite journal \| last=Laskey \| first=Kathryn B. \| last2=Laskey \| first2=Kenneth \| title=Service oriented architecture \| journal=WIREs Computational Statistics \| volume=1 \| issue=1 \|year=2009\| doi=10.1002/wics.8 \| page=101}}</ref> SOP provides a new technique to build agile application [[memory module\|modules]] using in-memory services as the unit of work.		'''Service-oriented programming''' (SOP) is a [[programming paradigm]] that uses "services" as the unit of computer work, to design and implement integrated business applications and [[mission critical]] software programs. Services can represent steps of [[business process]]es and thus one of the main applications of this paradigm is the cost-effective delivery of standalone or composite business applications that can "integrate from the inside-out". It inherently promotes [[service-oriented architecture]] (SOA), however, it is not the same as SOA. While SOA focuses on communication between systems using "services",<ref>{{cite journal \| last=Laskey \| first=Kathryn B. \| last2=Laskey \| first2=Kenneth \| title=Service oriented architecture \| journal=WIREs Computational Statistics \| volume=1 \| issue=1 \|year=2009\| doi=10.1002/wics.8 \| page=101}}</ref> SOP provides a new technique to build agile application [[memory module\|modules]] using in-memory services as the unit of work.