Link Details

Link 968735 thumbnail
User 478055 avatar

By mitchp
Published: May 15 2013 / 08:33

Originally mainframe architectures relied on a centralized host server that processed data and returned it to be displayed on a dummy terminal. These dummy terminals did not have my processing power and could only display data that was sent from the mainframe.
  • 7
  • 1
  • 471
  • 293


Add your comment
User 275298 avatar

pertra replied ago:

0 votes Vote down Vote up Reply

I'm not sure what you mean by a Mainframe Architecture. There are all kinds of solutions between the terminal (e.g. vt100, 3270 or x windows server) and other types of clients which differ by there "thinks". There are a reason why web-browsers are so popular: It is an advanced terminal, interpreting what the server (running e.g. Linux, Windows or z/OS) are giving them. Your application change for everyone when make you changes to the server. The disadvantages of a client/server solution can be a distributed client which can be a nightmare to maintain and update. So think of a Mainframe Architecture as a Client/Server architecture with a standard Client.

Add your comment

Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Voters For This Link (7)

Voters Against This Link (1)

Apache Hadoop
Written by: Piotr Krewski
Featured Refcardz: Top Refcardz:
  1. Play
  2. Akka
  3. Design Patterns
  4. OO JS
  5. Cont. Delivery
  1. Play
  2. Java Performance
  3. Akka
  4. REST
  5. Java