Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added input-processing-output #304

Merged
merged 1 commit into from
Feb 4, 2025
Merged

Added input-processing-output #304

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down