dido:public:ra:xapend:xapend.a_glossary:s:sw_stack
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.a_glossary:s:sw_stack [2022/01/16 07:00] nick |
dido:public:ra:xapend:xapend.a_glossary:s:sw_stack [2022/01/18 14:01] (current) nick |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| A **Software Stack** is comprised from a set of [[dido:public:ra:xapend:xapend.a_glossary:s:subsystem | Software Subsystems]] or [[dido:public:ra:xapend:xapend.a_glossary:c:component | Components]] connected together to create a complete [[dido:public:ra:xapend:xapend.a_glossary:p:platform]]. Once defined, a **Software Stack** is self-contained and requires no additional subsystems or components to support applications. Applications are said to **''run on''** or **''run on top of''** the resulting **Software Stack**. | A **Software Stack** is comprised from a set of [[dido:public:ra:xapend:xapend.a_glossary:s:subsystem | Software Subsystems]] or [[dido:public:ra:xapend:xapend.a_glossary:c:component | Components]] connected together to create a complete [[dido:public:ra:xapend:xapend.a_glossary:p:platform]]. Once defined, a **Software Stack** is self-contained and requires no additional subsystems or components to support applications. Applications are said to **''run on''** or **''run on top of''** the resulting **Software Stack**. | ||
| - | For example, to develop a web application, the architect defines the stack as the target [[dido:public:ra:xapend:xapend.a_glossary:o:os]], [[dido:public:ra:xapend:xapend.a_glossary:w:web_service | Web Server]], [[dido:public:ra:xapend:xapend.a_glossary:d:database]], and [[dido:public:ra:xapend:xapend.a_glossary:p:programlang]] environment. Another version of a software stack is operating system, middleware, database, and applications.[2] Regularly, the components of a software stack are developed by different developers independently from one another. | + | For example, to develop a web application, the architect defines the stack as the target [[dido:public:ra:xapend:xapend.a_glossary:o:os]], [[dido:public:ra:xapend:xapend.a_glossary:w:web_service | Web Server]], [[dido:public:ra:xapend:xapend.a_glossary:d:database]], and [[dido:public:ra:xapend:xapend.a_glossary:p:programlang]] environment. |
| - | Some components/subsystems of an overall system are chosen together often enough that the particular set is referred to by a name representing the whole, rather than by naming the parts. Typically, the name is an acronym representing the individual components.[3] | + | Another version of a **Software Stack** is operating system, middleware, database, and applications. Regularly, the Components of a **Software Stack** are developed by different developers independently of one another and are integrated together and single named entity, forming the basis for many systems. For example: |
| + | |||
| + | * [[https://cloudstack.apache.org/ | Apache CloudStack]] | ||
| + | * [[https://en.wikipedia.org/wiki/LAMP_(software_bundle) | LAMP (Linux, Apache, MySQL, PHP/Perl/Python) ]] | ||
| + | * [[https://docs.oracle.com/en/cloud/paas/cloud-stack-manager/csmug/oracle-cloud-stack-manager.html | Oracle Cloud Stack ]] | ||
| + | * [[https://www.ibm.com/docs/en/sc-and-ds/8.2.2?topic=services-web-service-protocol-stack | Web Service Protocol Stack]] | ||
| + | |||
| + | See also [[dido:public:ra:xapend:xapend.a_glossary:s:solution_stack]] | ||
| Source: [[https://en.wikipedia.org/wiki/Solution_stack ]] | Source: [[https://en.wikipedia.org/wiki/Solution_stack ]] | ||
dido/public/ra/xapend/xapend.a_glossary/s/sw_stack.1642334444.txt.gz · Last modified: 2022/01/16 07:00 by nick
