Centralized computing: Difference between revisions

Revision as of 22:02, 7 May 2023

Latest revision as of 12:14, 28 May 2025

(One intermediate revision by one other user not shown)

Line 1:

{{See also|Centralisation}}

The app uses N. to N. encryption preventing 3rd parties from accessing data while it transferred from sender to the recipient because of this what's up is generally considered safe for me

{{Refimprove |date=May 2014}}

'''Centralized computing''' is computing done at a central ___location, using [[Computer terminal|terminals]] that are attached to a central computer. The computer itself may control all the [[peripheral]]s directly (if they are physically connected to the central computer), or they may be attached via a [[terminal server]]. Alternatively, if the terminals have the capability, they may be able to connect to the central computer over the network. The terminals may be [[text terminal]]s or [[thin client]]s, for example.

It offers greater [[security]] over [[Decentralized computing|decentralized systems]] because all of the [[Process (computing)|processing]] is controlled in a central ___location. In addition, if one terminal breaks down, the user can simply go to another terminal and [[log in]] again, and all of their [[computer file|file]]s will still be accessible. Depending on the system, they may even be able to resume their [[session (computer science)|session]] from the point they were at before, as if nothing had happened.

This type of arrangement does have some disadvantages. The central computer performs the computing functions and controls the remote terminals. This type of system relies totally on the central computer. Should the central computer [[crash (computing)|crash]], the entire system will "go down" (i.e. will be unavailable).

Another disadvantage is that central computing relies heavily on the quality of administration and resources provided to its users. Should the central computer be inadequately supported by any means (e.g. size of home directories, problems regarding administration), then your usage will suffer greatly. The reverse situation, however, (i.e., a system supported better than your needs) is one of the key advantages to centralized computing.

== History ==

Line 7 ⟶ 15:

== Contemporary status ==

As of 2007, centralized computing is now coming back into fashion – to a certain extent. Cloud computing has had an important role in the return of centralized computing.<ref>{{Cite journal|last=Irion|first=Kristina|date=December 2012|title=Government Cloud Computing and National Data Sovereignty|url=http://dx.doi.org/10.1002/poi3.10|journal=Policy & Internet|volume=4|issue=3-4|pages=40–71|doi=10.1002/poi3.10|issn=1944-2866|url-access=subscription}}</ref> [[Thin client]]s have been used for many years by businesses to reduce [[total cost of ownership]], while [[web application]]s are becoming more popular because they can potentially be used on many types of computing device without any need for software installation. Already, however, there are signs that the pendulum is swinging back again, away from pure centralization, as [[thin client]] devices become more like [[diskless workstation]]s due to increased computing power, and web applications start to do more processing on the client side, with technologies such as [[AJAX]] and [[rich client]]s.

In addition, [[Mainframe computer|mainframe]]s are still being used for some mission-critical applications, such as payroll, or for processing day-to-day account transactions in banks. These mainframes will typically be accessed either using [[terminal emulator]]s (real terminal devices are not used much any more) or via modern front-ends such as [[web application]]s – or (in the case of automated access) [[Communications protocol|protocols]] such as [[web service]]s protocols.