From e96ae1397728f6fa303422ba23b91caffae8d3d9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Thomas=20G=C3=BCttler?= Date: Wed, 5 Aug 2020 17:25:13 +0200 Subject: [PATCH] Added input-processing-output --- README.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/README.md b/README.md index 42cd6197..4e2de3aa 100644 --- a/README.md +++ b/README.md @@ -894,6 +894,21 @@ See also: on Medium](https://medium.com/baseds/foraging-for-the-fallacies-of-distributed-computing-part-1-1b35c3b85b53) - [Deutsch's Fallacies, 10 Years After](http://java.sys-con.com/node/38665) +### Input-Processing-Output is what it is all about + +[input–process–output (IPO) model](https://en.wikipedia.org/wiki/IPO_model) + +There are a thousand tools, programming languages, principles. Finally, it is all this simple pattern: + +1. The method/system/tool gets some input +2. The method/system/tool does some processing +3. The method/system/tool creates some output. + +Example: A HTTP request and the corresponding HTTP response are the perfect examples. Stateless has +won, [CORBA](https://en.wikipedia.org/wiki/Common_Object_Request_Broker_Architecture) is dead. If you use OOP does not matter much for the caller/client. + + + ## Reading List If you have found these concepts interesting, you may enjoy the following books.