Programming model: Difference between revisions

Revision as of 08:30, 1 June 2016

Latest revision as of 12:02, 17 March 2025

(36 intermediate revisions by 32 users not shown)

Line 1:

{{Short description|Area of research}}

{{About| the definition of the term 'programming model'| classification of programming languages| Programming paradigm}}

{{More citations needed|date=January 2025}}

A '''Programming Model''', refers to the style of programming where execution is invoked by making what appear to be [[Programming library|library]] calls. Examples include the [[POSIX Thread]] library and Hadoop's [[MapReduce]].<ref>{{cite web

A '''programming model''' is an [[execution model]] coupled to an [[API]] or a particular pattern of code. In this style, there are actually two execution models in play: the execution model of the base [[programming language]] and the execution model of the programming model. An example is [[Apache_Spark|Spark]] where [[Java_language| Java]] is the base language, and Spark is the programming model. Execution may be based on what appear to be [[Programming library|library]] calls. Other examples include the [[POSIX Threads]] library and Hadoop's [[MapReduce]].<ref>{{cite web

| url = https://www.ibm.com/software/data/infosphereanalytics/hadoop/mapreduce/

| title = What is MapReduce

| author = IBM

| website = [[IBM]]

}}</ref> In both cases, the [[execution model]] is different from that of the base language in which the code is written. For example, the [[C programming language]] has no execution model for thread behavior. But thread behavior can be invoked from C syntax, by making, what appears to be, a call to a normal C library.

|access-date=2020-04-19

}}</ref> In both cases, the [[execution model]] of the programming model is different from that of the base language in which the code is written. For example, the [[C programming language]] has no behavior in its execution model for input/output or thread behavior. But threadsuch behavior can be invoked from C syntax, by making, what appears to be, a call to a normal C library.

What distinguishes a programming model from a normal library is that the behavior of the call cannot be understood in terms of the language the program is written in. For Theexample, the behavior of calls to the POSIX thread library cannot be understood in terms of the C language. The reason is that the call invokes an execution model that is different from the execution model of the language. This invocation of an outside execution model is the defining characteristic of a programming ''model'', in contrast to a programming ''language''.

In [[parallel computing]], the execution model often must expose features of the hardware in order to achieve high performance. The large amount of variation in parallel hardware causes a concurrent need for a similarly large number of parallel execution models. It is impractical to make a new language for each execution model, hence it is a common practice to invoke the behaviors of the parallel execution model behaviors via an API. HenceSo, muchmost of parallelthe programming effort is done via parallel programming models rather than parallel languages. Unfortunately, theThe terminology around such programming models tends to focus on the details of the hardware that inspired the execution model, and in that insular world the mistaken belief is formed that a programming model is only for the case when an execution model is closely matched to hardware features.<ref>{{cite web

| url = httpshttp://asccompss.llnlbsc.goves/content/assets/docs/exascale-pmWG.pdf

| title = COMP Superscalar Programming ModelsModel

| author = LLNL Lawrence Livermore National Labs

}}</ref><ref>{{cite web

| url = https://www.bsc.es/computer-sciences/grid-computing/comp-superscalar/programming-model

| title = Programming Model

| author = Barcelona Supercomputing Center

}}</ref>

==References==