Клиент–сервер моделі бетінің кодын көру

Бұл бетті өңдеуге рұқсатыңыз жоқ. Келесі себеппен:

Your IP address is in a range that has been blocked on all Wikimedia Foundation wikis.

The block was made by ‪EPIC‬. The reason given is Open proxy/Webhost: See the help page if you are affected.

Start of block: 13:48, 2024 ж. шілденің 2
Expiry of block: 13:48, 2025 ж. шілденің 2

Your current IP address is 206.189.44.186. The blocked range is 206.189.32.0/20.

Please include all above details in any queries you make. If you believe you were blocked by mistake, you can find additional information and instructions in the No open proxies global policy.

Otherwise, to discuss the block please post a request for review on Meta-Wiki. You could also send an email to the stewards VRT queue at stewards@wikimedia.org including all above details.

Бұл беттің кодын көріп, көшіре аласыз.

[[File:Two-tier architecture.ru.svg|thumb|right|200px|Екі деңгейлі архитектура мысалы.]]
'''Клиент–сервер моделі''' ({{lang-en|Client-server model}}) — есептеу техникасы архитектурасының моделі сервер мен клиент арасындағы [[клиент]] сұратқан қызмет сұратуларына [[сервер]]дің берген ресурс немесе қызметтер жұмыстарын бөліп таратып үйлестіріп тұратын үйлестірілген қосымша (distributed application) қызметі.<ref>{{cite web|url=http://java.sun.com/developer/Books/jdbc/ch07.pdf|publisher=Sun Microsystems|title=Distributed Application Architecture|accessdate=2009-06-16}}</ref>

<!--

The '''client/server model''' is a [[computing]] model that acts as a [[distributed application]] which partitions tasks or workloads between the providers of a resource or service, called [[server (computing)|server]]s, and service requesters, called [[client (computing)|client]]s.<ref>{{cite web|url=http://java.sun.com/developer/Books/jdbc/ch07.pdf|publisher=Sun Microsystem|title=Distributed Application Architecture|accessdate=2009-06-16}}</ref> Often clients and servers communicate over a [[computer network]] on separate hardware, but both client and server may reside in the same system. A server machine is a host that is running one or more server programs which share their resources with clients. A client does not share any of its resources, but requests a server's content or service function. Clients therefore initiate communication sessions with servers which await incoming requests.

[[File:Client-server-model.svg|thumb|Schematic clients-server interaction.]]

The ''client/server'' characteristic describes the relationship of cooperating programs in an application. The server component provides a function or service to one or many clients, which initiate requests for such services.  A notable example of this is the way [[OpenGL]] treats the video card of a computer as a server, with the actual application making rendering requests to it.  This model is further solidified with the [[GLSL|OpenGL Shading Language]], with the user writing small programs that live in video memory, and are requested from the main program through the graphics driver.

''Functions'' such as email exchange, web access and database access are built on the client/server model. Users accessing banking services from their computer use a web browser client to send a request to a web server at a bank. That web server runs a program which may in turn, forward the request to its own database client program, which sends a request to the bank's database server (which runs on another computer) to retrieve the account information. The balance and transaction records are returned to the bank database client, which in turn serves it back to the user's web browser client, displaying the results to the user.
The client–server model has become one of the central ideas of [[network computing]]. Many business applications being written today use the client–server model, as do the Internet's main application protocols, such as [[HTTP]], [[SMTP]], [[Telnet]], and [[Domain Name System|DNS]].

The interaction between client and server is often described using [[sequence diagram]]s. The [[Unified Modeling Language]] has support for sequence diagrams.

Specific types of clients include [[web browser]]s, [[email client]]s, and [[online chat]] clients.

Specific types of servers include [[web server]]s, [[ftp server]]s, [[application server]]s, [[database server]]s, [[name server]]s, [[mail server]]s, [[file server]]s, [[print server]]s, and [[terminal server]]s.  Most [[web service]]s are also types of servers.

 вычислительная или сетевая архитектура, в которой задания или сетевая нагрузка распределены между поставщиками услуг (сервисов), называемыми серверами, и заказчиками услуг, называемыми клиентами. Нередко клиенты и серверы взаимодействуют через компьютерную сеть и могут быть как различными физическими устройствами, так и [[Программное обеспечение | программным обеспечением]].

== Преимущества ==
* Отсутствие дублирования кода программы-сервера программами-клиентами.
* Так как все вычисления выполняются на сервере, то требования к компьютерам на которых установлен клиент снижаются.
* Все данные хранятся на сервере, который, как правило, защищён гораздо лучше большинства клиентов. На сервере проще обеспечить контроль полномочий, чтобы разрешать доступ к данным только клиентам с соответствующими правами доступа. 
* Позволяет объединить различные клиенты. Использовать ресурсы одного сервера часто могут клиенты с разными аппаратными платформами, операционными системами и т. п.
* Позволяет разгрузить сети за счёт того, что между сервером и клиентом передаются небольшие порции данных.

== Недостатки ==
* Неработоспособность сервера может сделать неработоспособной всю вычислительную сеть. Неработоспособным сервером следует считать сервер, производительности которого не хватает на обслуживание всех клиентов, а также сервер, находящийся на ремонте, профилактике и т. п.
* Поддержка работы данной системы требует отдельного специалиста — системного администратора.
* Высокая стоимость оборудования.

== Многоуровневая архитектура клиент-сервер ==
'''Многоуровневая архитектура клиент-сервер''' — разновидность архитектуры клиент-сервер, в которой функция обработки данных вынесена на один или несколько отдельных серверов. Это позволяет разделить функции хранения, обработки и представления данных для более эффективного использования возможностей серверов и клиентов.

Частные случаи многоуровневой архитектуры:
* [[Трёхуровневая архитектура]]

== Сеть с выделенным сервером ==

'''Сеть с выделенным сервером''' ({{lang-en|Client/Server network}}) — это [[локальная вычислительная сеть|локальная вычислительная сеть (LAN)]], в которой сетевые устройства централизованы и управляются одним или несколькими серверами. Индивидуальные рабочие станции или клиенты (такие, как ПК) должны обращаться к ресурсам сети через сервер(ы).

==Comparison to peer-to-peer architecture==

A client/server network involves multiple clients connecting to a single, central server. The file server on a client/server network must have robust hardware configurations to handle large volumes of client service requests. Hence servers usually are high speed computers with large hard disk capacity.

By contrast, [[peer-to-peer]] networks involve two or more computers pooling individual resources such as disk drives, CD-ROMs and printers.<ref>[http://www.isafe.org/imgs/pdf/education/P2PNetworking.pdf Understanding peer-to-peer networking]</ref> These shared resources are available to every computer in the network, while each of them communicates in a session. Each computer acts as both the client and the server which means all the computers on the network are equals, that is where the term peer-to-peer comes from. The advantage of peer-to-peer networking is the easier control concept not requiring any additional coordination entity and not delaying transfers by routing via server entities. However, the collision of session may be larger than with routing via server nodes.

In the peer to peer network, software applications can be installed on the single computer and shared by every computer in the network. They are also cheaper to set up because most desktop operating systems have the software required for the network installed by default. On the other hand, the client/server model works with any size or physical layout of LAN and doesn't tend to slow down with a heavy use.<ref>[Peer-to-Peer Networking and Applications]</ref>

Peer-to-peer networks are typically less secure than client/server networks because security is handled by the individual computers, not controlled and supervised on the network as a whole. The resources of the computers in the network can become congested as they have to support not only the workstation user, but also the requests from network users. It may be difficult to provide systemwide services when the client operating system typically used in this type of network is incapable of hosting the service.

Client/server networks with their additional capacities have a higher initial setup cost for networking than peer to peer networks. The long-term aspect of administering a client/server network with applications largely server-hosted surely saves administering effort compared to administering the application settings per each client. In addition the concentration of functions in performant servers allows for lower grade performance qualification of the clients.

It is possible to set up a server on a modern desktop computer, but it is recommended to consider investment in enterprise-wide server facilities with standardised choice of hardware and software and with a systematic and remotely operable administering strategy. It is easier to configure and manage the server hardware and software compared to the distributed administering requirements with a flock of computers.<ref>Book: Computers are your future</ref><ref>Peer to Peer vs. Client/Server Networks</ref>
-->

== Әдебиет ==

{{cite web
 | author        = Валерий Коржов
 | authorlink    = 
 | datepublished = 17 маусым 1997
 | url           = http://www.osp.ru/nets/1997/06/142618/
 | title         = Многоуровневые системы клиент-сервер
 | format        = 
 | work          = 
 | publisher     = Издательство Открытые системы
 | accessdate    = 2010-01-31
 | lang          = 
 | description   = 
 | archiveurl = http://www.webcitation.org/61DUMtwXO
 | archivedate = 2011-08-26
}}

==Тағы қараңыз ==
* Жауап коды

==Сілттемелер==
<references/>

[[Санат:Компьютер желілері архитектурасы]]
[[Санат:Ақпараттық технологиялар]]

Бұл бетте қолданылған үлгілер:

Үлгі:Cite web (өңдеу)
Үлгі:HumanizeDate (өңдеу)
Үлгі:Lang (кодын көру) (қорғалған)
Үлгі:Lang-en (кодын көру) (қорғалған)
Үлгі:LangWithName (кодын көру) (қорғалған)
Үлгі:Str left (өңдеу)

Клиент–сервер моделі бетіне қайту.

«https://kk.wikipedia.org/wiki/Клиент–сервер_моделі» бетінен алынған

Клиент–сервер моделі бетінің кодын көру

Навигация мәзірі

Іздеу