Client-Server Architectural Pattern

Client-Server Architectural Pattern
For the description below, the best pattern would be client-server architecture. This type of
architecture helps in separating components and allow them to work interdependently of one
another. A single server can provide services to multiple clients. Servers are always on
listening to clients. A client requests a service from a server through a communication
channel, the server provides the services and waits for the next client. Servers are literally
permanently active unless an incidence occurs.
Clients may reside in different machines from the servers hence a “mechanism to overcome
machine and process boundaries” (Architectural Patterns, 2018). Communication channels
involving wired or wireless communication can be used in client-server architecture to
connect the clients and the server. This type of “architecture can be seen as a layered pattern
where the clients are on the higher level and the server on the lower level’ (Architectural
Patterns, 2018).
Databases reside in server side and clients send requests to access the database. The server
grants the request and the clients are able to display data. Web interfaces are clients. An
example is when one is browsing a website like Facebook, the interface communicates with
the servers to be able to display user information.

The diagram below shows how a client-server architecture looks like:
TCP/IP
SERVER
CLIENT