Process-oriented programming: Difference between revisions

Revision as of 22:24, 2 August 2016

Latest revision as of 21:44, 18 August 2025

(6 intermediate revisions by 5 users not shown)

Line 1:

{{Programming paradigms}}

'''Process-oriented programming''' is a [[programming paradigm]] that separates the concerns of data structures and the concurrent processes that act upon them. The data structures in this case are typically persistent, complex, and large scale - the subject of general purpose applications, as opposed to specialized processing of specialized data sets seen in high productivity applications (HPC). The model allows the creation of large scale applications that partially share common data sets. Programs are functionally decomposed into parallel processes that create and act upon logically shared data.

The paradigm was originally invented for parallel computers in the 1980s, especially computers built with [[transputer]] microprocessors by [[INMOS]], or similar architectures. [[Occam programming language|Occam]] was an early process-oriented language developed for the Transputer.

Some derivations have evolved from the [[message passing]] paradigm of Occam to enable uniform efficiency when porting applications between [[distributed memory]] and [[shared memory]] parallel computers {{Citation needed|date=June 2012}}. The first such derived example appears in the programming language [[Ease programming language|Ease]] designed at Yale University<ref name="process">{{cite paperdocument | last=Ericsson-Zenith | title=Programming with Ease; Semiotic definition of the language|publisher=Yale University, Computer Science Technical Report YALEU/DCS/RR-809|year=1990}}</ref><ref name="process2">{{cite book | last=Ericsson-Zenith |title=Process Interaction Models|publisher=Paris University|year=1992}}</ref> in 1990. Similar models have appeared since in the loose combination of SQL databases and objected oriented languages such as [[Java (programming language)|Java]], often referred to as object-relational models and widely used in large scale distributed systems today. The paradigm is likely to appear on desktop computers as microprocessors increase the number of processors ([[Multi-core processor|multicore]]) per chip.

The [[Actor model]] might usefully be described as a specialisedspecialized kind of process-oriented system in which the message-passing model is restricted to the simple fixed case of one infinite [[input queue]] per process (i.e. actor), to which any other process can send messages.

==See also==

*[[Communicating process architectures]]

*[[Massively parallel processing]]

*[[Parallel computing]]

Line 20 ⟶ 17:

==External links==

* [http://digitalscholarship.unlv.edu/cgi/viewcontent.cgi?article=2392&context=thesesdissertations Sowders, Matthew, "ProcessJ: A process-oriented programming language" (2011). UNLV Theses, Dissertations, Professional Papers, and Capstones. Paper 1393.]

* [http://webdigg.net/Process/Process-Interaction-Models/ Process Interaction Models]

* [http://www.cs.unlv.edu/~matt/research/Joccam-content.html A new process oriented language with Java-like syntax targeting multiple execution architectures] {{dead link|date=June 2012}}

{{Programming paradigms navbox}}

[[Category:Programming paradigms]]