presentation layer process

How-To Geek

The 7 osi networking layers explained.

Your changes have been saved

Email is sent

Email has already been sent

Please verify your email address.

You’ve reached your account maximum for followed topics.

How to Take Better Night Sky Photos on a Google Pixel

Why i wish i started using onedrive sooner, this single feature makes new outlook for windows worth it, quick links.

• Physical Layer
• Data Link Layer
• Network Layer
• Transport Layer
• Session Layer
• Presentation Layer
• Application Layer

The Open Systems Interconnection (OSI) networking model defines a conceptual framework for communications between computer systems. The model is an ISO standard which identifies seven fundamental networking layers, from the physical hardware up to high-level software applications.

Each layer in the model handles a specific networking function. The standard helps administrators to visualize networks, isolate problems, and understand the use cases for new technologies. Many network equipment vendors advertise the OSI layer that their products are designed to slot into.

OSI was adopted as an international standard in 1984. It remains relevant today despite the changes to network implementation that have occurred since first publication. Cloud, edge, and IoT can all be accommodated within the model.

In this article, we'll explain each of the seven OSI layers in turn. We'll start from the lowest level, labelled as Layer 1.

1. Physical Layer

All networking begins with physical equipment. This layer encapsulates the hardware involved in the communications, such as switches and cables. Data is transferred as a stream of binary digits - 0 or 1 - that the hardware prepares from input it's been fed. The physical layer specifies the electrical signals that are used to encode the data over the wire, such as a 5-volt pulse to indicate a binary "1."

Errors in the physical layer tend to result in data not being transferred at all. There could be a break in the connection due to a missing plug or incorrect power supply. Problems can also arise when two components disagree on the physical encoding of data values. In the case of wireless connections, a weak signal can lead to bit loss during transmission.

2. Data Link Layer

The model's second layer concerns communication between two devices that are directly connected to each other in the same network. It's responsible for establishing a link that allows data to be exchanged using an agreed protocol. Many network switches operate at Layer 2.

The data link layer will eventually pass bits to the physical layer. As it sits above the hardware, the data link layer can perform basic error detection and correction in response to physical transfer issues. There are two sub-layers that define these responsibilities: Logical Link Control (LLC) that handles frame synchronization and error detection, and Media Access Control (MAC) which uses MAC addresses to constrain how devices acquire permission to transfer data.

3. Network Layer

The network layer is the first level to support data transfer between two separately maintained networks. It's redundant in situations where all your devices exist on the same network.

Data that comes to the network layer from higher levels is first broken up into packets suitable for transmission. Packets received from the remote network in response are reassembled into usable data.

The network layer is where several important protocols are first encountered. These include IP (for determining the path to a destination), ICMP, routing, and virtual LAN. Together these mechanisms facilitate inter-network communications with a familiar degree of usability. However operations at this level aren't necessarily reliable: messages aren't required to succeed and may not necessarily be retried.

4. Transport Layer

The transport layer provides higher-level abstractions for coordinating data transfers between devices. Transport controllers determine where data will be sent and the rate it should be transferred at.

Layer 4 is where TCP and UDP are implemented, providing the port numbers that allow devices to expose multiple communication channels. Load balancing is often situated at Layer 4 as a result, allowing traffic to be routed between ports on a target device.

Transport mechanisms are expected to guarantee successful communication. Stringent error controls are applied to recover from packet loss and retry failed transfers. Flow control is enforced so the sender doesn't overwhelm the remote device by sending data more quickly than the available bandwidth permits.

5. Session Layer

Layer 5 creates ongoing communication sessions between two devices. Sessions are used to negotiate new connections, agree on their duration, and gracefully close down the connection once the data exchange is complete. This layer ensures that sessions remain open long enough to transfer all the data that's being sent.

Checkpoint control is another responsibility that's held by Layer 5. Sessions can define checkpoints to facilitate progress updates and resumable transmissions. A new checkpoint could be set every few megabytes for a file upload, allowing the sender to continue from a particular point if the transfer gets interrupted.

Many significant protocols operate at Layer 5 including authentication and logon technologies such as LDAP and NetBIOS. These establish semi-permanent communication channels for managing an end user session on a specific device.

6. Presentation Layer

The presentation layer handles preparation of data for the application layer that comes next in the model. After data has made it up from the hardware, through the data link, and across the transport, it's almost ready to be consumed by high-level components. The presentation layer completes the process by performing any formatting tasks that may be required.

Decryption, decoding, and decompression are three common operations found at this level. The presentation layer processes received data into formats that can be eventually utilized by a client application. Similarly, outward-bound data is reformatted into compressed and encrypted structures that are suitable for network transmission.

TLS is one major technology that's part of the presentation layer. Certificate verification and data decryption is handled before requests reach the network client, allowing information to be consumed with confidence that it's authentic.

7. Application Layer

The application layer is the top of the stack. It represents the functionality that's perceived by network end users. Applications in the OSI model provide a convenient end-to-end interface to facilitate complete data transfers, without making you think about hardware, data links, sessions, and compression.

Despite its name, this layer doesn't relate to client-side software such as your web browser or email client. An application in OSI terms is a protocol that caters for the complete communication of complex data through layers 1-6.

HTTP, FTP, DHCP, DNS, and SSH all exist at the application layer. These are high-level mechanisms which permit direct transfers of user data between an origin device and a remote server. You only need minimal knowledge of the workings of the other layers.

The seven OSI layers describe the transfer of data through computer networks. Understanding the functions and responsibilities of each layer can help you identify the source of problems and assess the intended use case for new components.

OSI is an abstract model that doesn't directly map to the specific networking implementations commonly used today. As an example, the TCP/IP protocol works on its own simpler system of four layers: Network Access, Internet, Transport, and Application. These abstract and absorb the equivalent OSI layers: the application layer spans OSI L5 to L7, while L1 and L2 are combined in TCP/IP's concept of Network Access.

OSI remains applicable despite its lack of direct real-world application. It's been around so long that it's widely understood among administrators from all backgrounds. Its relatively high level of abstraction has also ensured it's remained relevant in the face of new networking paradigms, many of which have targeted Layer 3 and above. An awareness of the seven layers and their responsibilities can still help you appreciate the flow of data through a network while uncovering integration opportunities for new components.

• Engineering Mathematics
• Discrete Mathematics
• Operating System
• Computer Networks
• Digital Logic and Design
• C Programming
• Data Structures
• Theory of Computation
• Compiler Design
• Computer Org and Architecture

What is OSI Model? – Layers of OSI Model

OSI stands for Open Systems Interconnection , where open stands to say non-proprietary. It is a 7-layer architecture with each layer having specific functionality to perform. All these 7 layers work collaboratively to transmit the data from one person to another across the globe. The OSI reference model was developed by ISO – ‘International Organization for Standardization ‘, in the year 1984.

The OSI model provides a theoretical foundation for understanding network communication . However, it is usually not directly implemented in its entirety in real-world networking hardware or software . Instead, specific protocols and technologies are often designed based on the principles outlined in the OSI model to facilitate efficient data transmission and networking operations

What is OSI Model?

• What are the 7 layers of the OSI Model?

Physical Layer – Layer 1

Data link layer (dll) – layer 2, network layer – layer 3, transport layer – layer 4, session layer – layer 5, presentation layer – layer 6, application layer – layer 7.

• What is the Flow of Data in OSI Model?

Advantages of OSI Model

• OSI Model in a Nutshell

OSI vs TCP/IP Model

The OSI model, created in 1984 by ISO , is a reference framework that explains the process of transmitting data between computers. It is divided into seven layers that work together to carry out specialised network functions , allowing for a more systematic approach to networking.

For those preparing for competitive exams like GATE, a strong understanding of networking concepts, including the OSI model, is crucial. To deepen your knowledge in this area and other key computer science topics, consider enrolling in the GATE CS Self-Paced course . This course offers comprehensive coverage of the syllabus, helping you build a solid foundation for your exam preparation.

Data Flow In OSI Model

When we transfer information from one device to another, it travels through 7 layers of OSI model. First data travels down through 7 layers from the sender’s end and then climbs back 7 layers on the receiver’s end.

Data flows through the OSI model in a step-by-step process:

• Application Layer: Applications create the data.
• Presentation Layer: Data is formatted and encrypted.
• Session Layer: Connections are established and managed.
• Transport Layer: Data is broken into segments for reliable delivery.
• Network Layer : Segments are packaged into packets and routed.
• Data Link Layer: Packets are framed and sent to the next device.
• Physical Layer: Frames are converted into bits and transmitted physically.

Each layer adds specific information to ensure the data reaches its destination correctly, and these steps are reversed upon arrival.

Let’s look at it with an Example:

Luffy sends an e-mail to his friend Zoro.

Step 1: Luffy interacts with e-mail application like Gmail , outlook , etc. Writes his email to send. (This happens in Layer 7: Application layer )

Step 2: Mail application prepares for data transmission like encrypting data and formatting it for transmission. (This happens in Layer 6: Presentation Layer )

Step 3: There is a connection established between the sender and receiver on the internet. (This happens in Layer 5: Session Layer )

Step 4: Email data is broken into smaller segments. It adds sequence number and error-checking information to maintain the reliability of the information. (This happens in Layer 4: Transport Layer )

Step 5: Addressing of packets is done in order to find the best route for transfer. (This happens in Layer 3: Network Layer )

Step 6: Data packets are encapsulated into frames, then MAC address is added for local devices and then it checks for error using error detection. (This happens in Layer 2: Data Link Layer )

Step 7: Lastly Frames are transmitted in the form of electrical/ optical signals over a physical network medium like ethernet cable or WiFi.

After the email reaches the receiver i.e. Zoro, the process will reverse and decrypt the e-mail content. At last, the email will be shown on Zoro’s email client.

What Are The 7 Layers of The OSI Model?

The OSI model consists of seven abstraction layers arranged in a top-down order:

• Physical Layer
• Data Link Layer
• Network Layer
• Transport Layer
• Session Layer
• Presentation Layer
• Application Layer

The lowest layer of the OSI reference model is the physical layer. It is responsible for the actual physical connection between the devices. The physical layer contains information in the form of bits. It is responsible for transmitting individual bits from one node to the next. When receiving data, this layer will get the signal received and convert it into 0s and 1s and send them to the Data Link layer, which will put the frame back together.

Functions of the Physical Layer

• Bit Synchronization: The physical layer provides the synchronization of the bits by providing a clock. This clock controls both sender and receiver thus providing synchronization at the bit level.
• Bit Rate Control: The Physical layer also defines the transmission rate i.e. the number of bits sent per second.
• Physical Topologies: Physical layer specifies how the different, devices/nodes are arranged in a network i.e. bus, star, or mesh topology.
• Transmission Mode: Physical layer also defines how the data flows between the two connected devices. The various transmission modes possible are Simplex, half-duplex and full-duplex.

Note: Hub, Repeater, Modem, and Cables are Physical Layer devices. Network Layer, Data Link Layer, and Physical Layer are also known as Lower Layers or Hardware Layers .

The data link layer is responsible for the node-to-node delivery of the message. The main function of this layer is to make sure data transfer is error-free from one node to another, over the physical layer. When a packet arrives in a network, it is the responsibility of the DLL to transmit it to the Host using its MAC address . The Data Link Layer is divided into two sublayers:

• Logical Link Control (LLC)
• Media Access Control (MAC)

The packet received from the Network layer is further divided into frames depending on the frame size of the NIC(Network Interface Card). DLL also encapsulates Sender and Receiver’s MAC address in the header.

The Receiver’s MAC address is obtained by placing an ARP(Address Resolution Protocol) request onto the wire asking “Who has that IP address?” and the destination host will reply with its MAC address.

Functions of the Data Link Layer

• Framing: Framing is a function of the data link layer. It provides a way for a sender to transmit a set of bits that are meaningful to the receiver. This can be accomplished by attaching special bit patterns to the beginning and end of the frame.
• Physical Addressing: After creating frames, the Data link layer adds physical addresses ( MAC addresses ) of the sender and/or receiver in the header of each frame.
• Error Control: The data link layer provides the mechanism of error control in which it detects and retransmits damaged or lost frames.
• Flow Control: The data rate must be constant on both sides else the data may get corrupted thus, flow control coordinates the amount of data that can be sent before receiving an acknowledgment.
• Access Control: When a single communication channel is shared by multiple devices, the MAC sub-layer of the data link layer helps to determine which device has control over the channel at a given time.

Note: Packet in the Data Link layer is referred to as Frame. Data Link layer is handled by the NIC (Network Interface Card) and device drivers of host machines. Switch & Bridge are Data Link Layer devices.

The network layer works for the transmission of data from one host to the other located in different networks. It also takes care of packet routing i.e. selection of the shortest path to transmit the packet, from the number of routes available. The sender & receiver’s IP address es are placed in the header by the network layer.

Functions of the Network Layer

• Routing: The network layer protocols determine which route is suitable from source to destination. This function of the network layer is known as routing.
• Logical Addressing: To identify each device inter-network uniquely, the network layer defines an addressing scheme. The sender & receiver’s IP addresses are placed in the header by the network layer. Such an address distinguishes each device uniquely and universally.

Note: Segment in the Network layer is referred to as Packet . Network layer is implemented by networking devices such as routers and switches.

The transport layer provides services to the application layer and takes services from the network layer. The data in the transport layer is referred to as Segments . It is responsible for the end-to-end delivery of the complete message. The transport layer also provides the acknowledgment of the successful data transmission and re-transmits the data if an error is found.

At the sender’s side: The transport layer receives the formatted data from the upper layers, performs Segmentation , and also implements Flow and error control to ensure proper data transmission. It also adds Source and Destination port number s in its header and forwards the segmented data to the Network Layer.

Note: The sender needs to know the port number associated with the receiver’s application. Generally, this destination port number is configured, either by default or manually. For example, when a web application requests a web server, it typically uses port number 80, because this is the default port assigned to web applications. Many applications have default ports assigned.

At the receiver’s side: Transport Layer reads the port number from its header and forwards the Data which it has received to the respective application. It also performs sequencing and reassembling of the segmented data.

Functions of the Transport Layer

• Segmentation and Reassembly: This layer accepts the message from the (session) layer, and breaks the message into smaller units. Each of the segments produced has a header associated with it. The transport layer at the destination station reassembles the message.
• Service Point Addressing: To deliver the message to the correct process, the transport layer header includes a type of address called service point address or port address. Thus by specifying this address, the transport layer makes sure that the message is delivered to the correct process.

Services Provided by Transport Layer

• Connection-Oriented Service
• Connectionless Service

1. Connection-Oriented Service: It is a three-phase process that includes:

• Connection Establishment
• Data Transfer
• Termination/disconnection

In this type of transmission, the receiving device sends an acknowledgment, back to the source after a packet or group of packets is received. This type of transmission is reliable and secure.

2. Connectionless service: It is a one-phase process and includes Data Transfer. In this type of transmission, the receiver does not acknowledge receipt of a packet. This approach allows for much faster communication between devices. Connection-oriented service is more reliable than connectionless Service.

Note: Data in the Transport Layer is called Segments . Transport layer is operated by the Operating System. It is a part of the OS and communicates with the Application Layer by making system calls. The transport layer is called as Heart of the OSI model. Device or Protocol Use : TCP, UDP  NetBIOS, PPTP

This layer is responsible for the establishment of connection, maintenance of sessions, and authentication, and also ensures security.

Functions of the Session Layer

• Session Establishment, Maintenance, and Termination: The layer allows the two processes to establish, use, and terminate a connection.
• Synchronization: This layer allows a process to add checkpoints that are considered synchronization points in the data. These synchronization points help to identify the error so that the data is re-synchronized properly, and ends of the messages are not cut prematurely and data loss is avoided.
• Dialog Controller: The session layer allows two systems to start communication with each other in half-duplex or full-duplex.

Note: All the below 3 layers(including Session Layer) are integrated as a single layer in the TCP/IP model as the “Application Layer”. Implementation of these 3 layers is done by the network application itself. These are also known as Upper Layers or Software Layers. Device or Protocol Use : NetBIOS, PPTP.

Let us consider a scenario where a user wants to send a message through some Messenger application running in their browser. The “ Messenger ” here acts as the application layer which provides the user with an interface to create the data. This message or so-called Data is compressed, optionally encrypted (if the data is sensitive), and converted into bits (0’s and 1’s) so that it can be transmitted.

Communication in Session Layer

The presentation layer is also called the Translation layer . The data from the application layer is extracted here and manipulated as per the required format to transmit over the network.

Functions of the Presentation Layer

• Translation: For example, ASCII to EBCDIC .
• Encryption/ Decryption: Data encryption translates the data into another form or code. The encrypted data is known as the ciphertext and the decrypted data is known as plain text. A key value is used for encrypting as well as decrypting data.
• Compression: Reduces the number of bits that need to be transmitted on the network.

Note: Device or Protocol Use: JPEG, MPEG, GIF.

At the very top of the OSI Reference Model stack of layers, we find the Application layer which is implemented by the network applications. These applications produce the data to be transferred over the network. This layer also serves as a window for the application services to access the network and for displaying the received information to the user.

Example : Application – Browsers, Skype Messenger, etc.

Note: The application Layer is also called Desktop Layer. Device or Protocol Use : SMTP .

Functions of the Application Layer

The main functions of the application layer are given below.

• Network Virtual Terminal(NVT): It allows a user to log on to a remote host.
• File Transfer Access and Management(FTAM): This application allows a user to access files in a remote host, retrieve files in a remote host, and manage or control files from a remote computer.
• Mail Services: Provide email service.
• Directory Services: This application provides distributed database sources and access for global information about various objects and services.

Note: The OSI model acts as a reference model and is not implemented on the Internet because of its late invention. The current model being used is the TCP/IP model.

OSI Model – Layer Architecture

TCP/IP protocol ( Transfer Control Protocol/Internet Protocol ) was created by U.S. Department of Defense’s Advanced Research Projects Agency (ARPA) in 1970s.

Some key differences between the OSI model and the TCP/IP Model are:

• TCP/IP model consists of 4 layers but OSI model has 7 layers. Layers 5,6,7 of the OSI model are combined into the Application Layer of TCP/IP model and OSI layers 1 and 2 are combined into Network Access Layers of TCP/IP protocol.
• The TCP/IP model is older than the OSI model, hence it is a foundational protocol that defines how should data be transferred online.
• Compared to the OSI model, the TCP/IP model has less strict layer boundaries.
• All layers of the TCP/IP model are needed for data transmission but in the OSI model, some applications can skip certain layers. Only layers 1,2 and 3 of the OSI model are necessary for data transmission.

OSI vs TCP/IP

Why Does The OSI Model Matter?

Even though the modern Internet doesn’t strictly use the OSI Model (it uses a simpler Internet protocol suite), the OSI Model is still very helpful for solving network problems. Whether it’s one person having trouble getting their laptop online, or a website being down for thousands of users, the OSI Model helps to identify the problem. If you can narrow down the issue to one specific layer of the model, you can avoid a lot of unnecessary work.

Imperva Application Security

Imperva security solutions protect your applications at different levels of the OSI model. They use DDoS mitigation to secure the network layer and provide web application firewall (WAF), bot management, and API security to protect the application layer.

To secure applications and networks across the OSI stack, Imperva offers multi-layered protection to ensure websites and applications are always available, accessible, and safe. The Imperva application security solution includes:

• DDoS Mitigation: Protects the network layer from Distributed Denial of Service attacks.
• Web Application Firewall (WAF) : Shields the application layer from threats.
• Bot Management: Prevents malicious bots from affecting the application.
• API Security: Secures APIs from various vulnerabilities and attacks.

The OSI Model defines the communication of a computing system into 7 different layers. Its advantages include:

• It divides network communication into 7 layers which makes it easier to understand and troubleshoot.
• It standardizes network communications, as each layer has fixed functions and protocols.
• Diagnosing network problems is easier with the OSI model .
• It is easier to improve with advancements as each layer can get updates separately.

Disadvantages of OSI Model

• Complexity: The OSI Model has seven layers, which can be complicated and hard to understand for beginners.
• Not Practical: In real-life networking, most systems use a simpler model called the Internet protocol suite (TCP/IP), so the OSI Model isn’t always directly applicable.
• Slow Adoption: When it was introduced, the OSI Model was not quickly adopted by the industry, which preferred the simpler and already-established TCP/IP model.
• Overhead: Each layer in the OSI Model adds its own set of rules and operations, which can make the process more time-consuming and less efficient.
• Theoretical: The OSI Model is more of a theoretical framework, meaning it’s great for understanding concepts but not always practical for implementation.

In conclusion, the OSI (Open Systems Interconnection) model is a conceptual framework that standardizes the functions of a telecommunication or computing system into seven distinct layers: Physical, Data Link, Network, Transport, Session, Presentation, and Application. Each layer has specific responsibilities and interacts with the layers directly above and below it, ensuring seamless communication and data exchange across diverse network environments. Understanding the OSI model helps in troubleshooting network issues, designing robust network architectures, and facilitating interoperability between different networking products and technologies.

Frequently Asked Questions on OSI Model – FAQs

Is osi layer still used.

Yes, the OSI model is still used by networking professionals to understand data abstraction paths and processes better.

What is the highest layer of the OSI model?

Layer 7 or Application layer is highest layer of OSI model.

What is layer 8?

Layer 8 doesn’t actually exist in the OSI model but is often jokingly used to refer to the end user. For example: a layer 8 error would be a user error.

Please Login to comment...

Similar reads.

• Best Twitch Extensions for 2024: Top Tools for Viewers and Streamers
• Discord Emojis List 2024: Copy and Paste
• Best Adblockers for Twitch TV: Enjoy Ad-Free Streaming in 2024
• PS4 vs. PS5: Which PlayStation Should You Buy in 2024?
• 10 Best Free VPN Services in 2024

Improve your Coding Skills with Practice

What kind of Experience do you want to share?

OSI Seven Layers Model Explained with Examples

This tutorial explains the OSI reference model. Learn the seven layers of the OSI model and the functions of each layer in detail through examples.

The OSI (Open System Interconnection) reference model is a comprehensive set of standards and rules for hardware manufacturers and software developers. By following these standards, they can build networking components and software applications that work in any environment. It was published in 1984 by ISO (International Organization for Standardization).

It provides a framework for creating and implementing networking standards, devices, and internetworking schemes. It explains the networking from a modular perspective, making it easier to understand and troubleshoot.

Seven layers of the OSI Model

The OSI model has seven different layers, which are divided into two groups. The following table lists all the layers with their names and numbers.

Let’s understand each layer in detail.

This tutorial is the second part of the article " Networking reference models explained in detail with examples. ". Other parts of this article are the following.

This tutorial is the first part of the article. It summarizes why the OSI model was created and what advantages it has.

This tutorial is the third part of the article. It compares the OSI reference model with the TCP/IP model and lists the similarities and differences between both.

This tutorial is the fourth part of the article. It explains the five layers of the TCP/IP model in detail.

This tutorial is the fifth part of the article. It explains how data is encapsulated and de-encapsulated when it passes through the layers.

The Application Layer

This is the last and topmost layer of the OSI model. This layer provides an interface between the local system and the application program running on the network. If an application wants to use the resources available on the remote system, it interacts with this layer. Then, this layer provides the protocols and services that the application needs to access those resources.

There are two types of application programs: Network-aware and Network-unaware . An application program is considered a Network-aware application if it can make any type of network request. If an application program cannot make any type of network request, it is considered a Network-unaware program.

Network-aware programs are further divided into two types.

Programs that are mainly built to work on a local system. This type of program occasionally accesses the network for particular reasons such as updates, documentation, and troubleshooting. MS-Word, Adobe-Photoshop, and VLC Player are examples of this type of program.

Programs that are mainly built to work with a remote system. This type of program provides a platform to access resources available on a remote system. This type of program only works if the system is connected to the network. SSH, FTP, and TFTP are examples of this type of program.

The Application layer describes only the programs which fall in the second type. But it doesn’t mean that the first type of programs can’t take the advantage of the Application layer. It simply means that they are not documented in the Application layer. But if required, they can also connect to the network through the Application layer.

The Top layer of the OSI model is the application layer. It provides the protocols and services that are required by the network-aware applications to connect to the network. FTP, TFTP, POP3, SMTP, and HTTP are examples of standards and protocols used in this layer.

The Presentation Layer

The sixth layer of the OSI model is the Presentation layer. Applications running on the local system may or may not understand the format that is used to transmit the data over the network. The presentation layer works as a translator. When receiving data from the Application layer, it converts that data in such a format that can be sent over the network. When receiving data from the Session layer, it reconverts the data in such a format that the application, which will use it, can understand.

Conversion, compression, and encryption are the main functions that the Presentation layer performs on the sending computer while on the receiving computer these functions are reconversion, decompression, and decryption. ASCII, BMP, GIF, JPEG, WAV, AVI, and MPEG are examples of standards and protocols that work in this layer.

The Session Layer

The session layer is the fifth layer of the OSI model. It is responsible for setting up, managing, and dismantling sessions between presentation layer entities and providing dialogs between computers.

When an application makes a network request, this layer checks whether the requested resource is available on the local system or on a remote system. If the requested resource is available on a remote system, it tests whether a network connection to access that resource is available or not. If a network connection is not available, it sends an error message back to the application informing that the connection is not available.

If a network connection is available, it establishes a session with the remote system. For each request, it uses a separate session. This allows multiple applications to send or receive data simultaneously. When data transmission is completed, it terminates the session.

The session layer is responsible for establishing, managing, and terminating communications between two computers. RPCs and NFS are examples of the session layer.

The Transport Layer

The transport layer is the fourth layer of the OSI model. It provides the following functionalities: -

Segmentation

On the sending computer, it breaks the data stream into smaller pieces. Each piece is known as a segment and the process of breaking the data stream into smaller pieces is known as the segmentation . On the receiving computer, it joins all segments to recreate the original data stream.

Data transportation

This layer establishes a logical connection between the sending system and receiving system and uses that connection to provide end-to-end data transportation. This process uses two protocols: TCP and UDP.

The TCP protocol is used for reliable data transportation. TCP is a connection-oriented protocol. UDP protocol is used for unreliable data transportation. UDP is a connection-less protocol.

The main difference between a connection-less and connection-oriented protocol is that a connection-oriented protocol provides reliable data delivery. For reliable data delivery, it uses several mechanisms such as the three-way handshake process, acknowledgments, sequencing, and flow control.

Multiplexing

Through the use of port numbers, this layer also provides connection multiplexing. Connection multiplexing allows multiple applications to send and receive data simultaneously.

The main functionalities of the Transport layer are segmentation, data transportation, and connection multiplexing. For data transportation, it uses TCP and UDP protocols. TCP is a connection-oriented protocol. It provides reliable data delivery.

The Network Layer

The third layer of the OSI model is the Network Layer. This layer takes the data segment from the Transport layer and adds a logical address to it. A logical address has two components; network partition and host partition. The Network partition is used to group networking components while the host partition is used to uniquely identify a system on the network. A logical address is known as the IP address. Once the logical address and other related information are added to the segment , it becomes the packet .

This layer decides whether the packet is intended for the local system or a remote system. It also specifies the standards and protocols which are used to move data packets over networks.

To move data packets between two different networks, a device known as the router is used. Routers use the logical address to make the routing decision. Routing is the process of forwarding data packets to their destination.

Defining logical addresses and finding the best path to reach the destination address are the main functions of this layer. Routers work in this layer. Routing also takes place in this layer. IP, IPX, and AppleTalk are examples of this layer.

The Data Link Layer

The Data Link Layer is the second layer of the OSI model. This layer defines how networking components access the media and what transmission methods they use. This layer has two sub-layers: MAC and LLC.

MAC (Media Access Control)

This sub-layer defines how the data packets are placed in media. It also provides physical addressing. The physical address is known as the MAC address. Unlike logical addresses that need to be configured, physical addresses are pre-configured in NIC. The MAC address is used to uniquely identify a host in the local network.

LLC (Logical Link Control)

This sub-layer identifies the network layer protocol. On the sending computer, it encapsulates the information of the Network Layer protocol in the LLC header from which the Data Link layer receives the data packet. On the receiving computer, it checks the LLC header to get the information about the network layer protocol. This way, a data packet is always delivered to the same network layer protocol from which it was sent.

Defining physical addresses, finding hosts in the local network, specifying standards and methods to access the media are the primary functions of this layer. Switching takes place in this layer. Switches and Bridges work in this layer. HDLC, PPP, and Frame Relay are examples of this layer.

The Physical Layer

The Physical Layer is the first layer of the OSI model. This layer specifies the standards for devices, media, and technologies that are used in moving the data across the network such as:-

• Type of cable used in connecting the devices
• Patterns of pins used in both sides of the cable
• Type of interface-card used in the networking device
• Type of connector used to connect the cable with the network interface
• Encoding of digital signals received from the Data Link layer based on the attached media type such as electrical for copper, light for fiber, or a radio wave for wireless.

On the sending computer, it converts digital signals received from the Data Link layer, into analog signals and loads them on the physical media. On the receiving computer, it picks analog signals from the media and converts them into digital signals, and transfers them to the Data Link layer for further processing.

The Physical Layer mainly defines standards for media and devices that are used to move data across the network. 10BaseT, 10Base100, CSU/DSU, DCE, and DTE are examples of the standards used in this layer.

That’s all for this tutorial. In the next part of this article, we will compare the OSI model with the TCP/IP model and explains the similarities and differences between both models. If you like this tutorial, please don’t forget to share it with friends.

By ComputerNetworkingNotes Updated on 2024-06-09

ComputerNetworkingNotes CCNA Study Guide OSI Seven Layers Model Explained with Examples

• EtherChannel Load Distribution Explained
• Link Aggregation Control Protocol (LACP) Explained
• Port Aggregation Protocol (PAgP) Explained
• EtherChannel Manual Configuration
• EtherChannel Basic Concepts Explained
• STP, RSTP, PVST, RPVST, and MSTP
• Similarities and Differences between STP and RSTP
• RSTP / RPVST Explained with Examples
• PVST/RPVST and EtherChannel Explained
• STP/RSTP Timers Explained

We do not accept any kind of Guest Post. Except Guest post submission, for any other query (such as adverting opportunity, product advertisement, feedback, suggestion, error reporting and technical issue) or simply just say to hello mail us [email protected]

Understanding the Role of the Presentation Layer in Data Format Translation and Security

2022/08/23 ・ computer networking, 1. introduction.

According to a recent study conducted by the Institute of Electrical and Electronics Engineers (IEEE), the presentation layer is responsible for ensuring that the data is in a format that is acceptable to the application layer. This includes data compression and decompression, encryption and decryption, and character set conversion. In today’s data-driven world, the ability to effectively manage and secure data is becoming increasingly important, and understanding the role of the presentation layer in this process is crucial.

This article will explore the techniques and technologies used in the presentation layer to perform data format translation, compression and decompression, and encryption and decryption. This will include a discussion of the benefits and limitations of these techniques, as well as real-life examples and case studies of their implementation. By the end of this article, readers will have a solid understanding of the role and functions of the presentation layer in the OSI model and how it contributes to secure and efficient data transmission.

2. The role of the presentation layer

The presentation layer, also known as the syntax layer, is the sixth layer in the OSI model. It ensures that the data is in a format acceptable to the application layer. This includes data format translation, compression and decompression, encryption and decryption, and character set conversion. It acts as an interface between the application layer and the rest of the layers in the OSI model.

Data Format Translation:

The presentation layer is responsible for translating data between different formats so the application layer can understand it. For example, it may convert a file from one format, such as TIFF, to another format, such as JPEG. This ensures that the data is in a form that is compatible with the application layer and can be processed accordingly.

Compression and Decompression:

Another essential function of the presentation layer is data compression and decompression. The layer compresses the data before sending it to the next layer, the network layer. This reduces the amount of data that needs to be transmitted, reducing the time required for the data to be shared. Once the data reaches the destination, the decompression process takes place, and the data is restored to its original form. There are various compression and decompression techniques like LZ77, LZ78, and Huffman coding that are used to compress and decompress data.

3. Data compression and decompression techniques

Data compression and decompression are essential functions of the presentation layer in the OSI model. Compression refers to reducing the amount of data that needs to be transmitted. At the same time, decompression restores the data to its original form once it reaches the destination. The use of compression techniques can significantly reduce the amount of time required for data to be transmitted, as well as reduce the bandwidth needed for transmission.

The presentation layer’s most commonly used compression techniques include LZ77, LZ78, and Huffman coding.

LZ77 is a lossless data compression algorithm that Abraham Lempel and Jacob Ziv first introduced in 1977. It replaces repeated instances of a data string concerning the original series. LZ77 is a dictionary-based algorithm that uses a sliding window to identify and replace repeated data instances. This technique is effective at compressing data that contains many repeated patterns, but it can be less effective on highly random data.

LZ78 is another lossless data compression algorithm that Lempel and Ziv introduced in 1978. It is similar to LZ77 but uses a different data compression approach. Instead of using a sliding window, LZ78 uses a dictionary of previously encountered data strings. This approach allows LZ78 to achieve higher compression ratios than LZ77 but also requires more memory and processing power.

Huffman coding:

Huffman coding is a lossless data compression algorithm introduced by David Huffman in 1952. Huffman coding is a variable-length coding algorithm that assigns shorter codes to more frequently occurring symbols in the data. This technique is especially effective for compressing data that contains many repeating characters, such as text or DNA sequences.

Each technique has its advantages and disadvantages; LZ77 and LZ78 are simpler than Huffman coding and can be implemented quickly. With a limited amount of memory, on the other hand, Huffman coding is more efficient in terms of compression ratio, but it is more complex and memory-intensive.

In real-life examples, all three algorithms have been used in various applications. For instance, LZ77 has been used to compress data in the telecommunications industry, and LZ78 has been used in data storage devices like hard drives and flash drives. In contrast, Huffman coding compresses text, images, audio and video files.

4. Encryption and decryption in the presentation layer

Encryption and decryption are essential security measures that are used to protect sensitive information as it is transmitted over a network. In the OSI model, encryption and decryption occur at the presentation layer. The presentation layer is responsible for ensuring that the data is in a format acceptable to the application layer, and it also ensures that the information is protected during transmission.

Encryption refers to converting plain text into an unreadable form, known as ciphertext. The ciphertext can only be read and understood by someone with the correct decryption key. Decryption, on the other hand, is the process of converting ciphertext back into plain text using the right decryption key.

The importance of encryption and decryption in the presentation layer is clear, especially with the rise of cyber threats. It ensures that only authorised parties can access and understand the sensitive information being transmitted. Without encryption and decryption, sensitive data would be vulnerable to eavesdropping and tampering.

There are two main types of encryption and decryption methods that are commonly used in the presentation layer: symmetric key encryption and asymmetric key encryption.

Symmetric key encryption:

Symmetric key encryption is a method of encryption where the same key is used for both encryption and decryption. This method is fast and efficient, but it also has some drawbacks. The main disadvantage is that the key must be securely exchanged between the sender and the receiver before any encryption can occur.

Asymmetric key encryption:

Asymmetric key encryption, also known as public key encryption, is a method of encryption where a pair of keys is used. One key is used for encryption, and the other is used for decryption. This method is more secure than symmetric key encryption because the key used for encryption can be made public, while the key used for decryption is kept private.

In real life, symmetric key encryption is used for bulk encryption, for example, in the transportation of email, instant messaging and other types of data where the speed of encryption is more important than key exchange. On the other hand, Asymmetric key encryption is often used for digital signatures, online transactions and handshaking in secure connections.

5. Common Attacks on the Presentation Layer

The Presentation Layer in the OSI model ensures data security during transmission. However, like any other layer in the OSI model, it is also vulnerable to various attacks, vulnerabilities, and threats. These can have severe consequences, such as unauthorised access or manipulation of sensitive information.

One standard attack on the presentation layer is a “format string attack”. This occurs when an attacker can insert random formatting characters into a string, which can then be used to disrupt the normal execution of a program. This can lead to various consequences, including buffer overflows, which can be used to execute arbitrary code or crash the system.

Another attack that targets the presentation layer is “malicious code injection”. This occurs when an attacker can insert malicious code into a seemingly benign file or message. This can be done by exploiting vulnerabilities in data format translation or compression/decompression mechanisms. Once the malicious code is executed, it can cause various types of damage, such as data loss, unauthorised access to sensitive information, or even complete system compromise.

In addition to these specific attacks, the presentation layer is vulnerable to more general threats, such as “man-in-the-middle” or “replay” attacks. These are attacks in which an attacker intercepts and alters communications between two parties to gain unauthorised access to sensitive information. Such attacks can occur on any OSI model layer, but they are particularly dangerous when they target the presentation layer, as the attacker can manipulate or intercept data in transit.

6. How to Secure the Presentation Layer

Securing the Presentation Layer in the OSI model is crucial for protecting sensitive information during transmission. There are various security best practices that organisations can implement to protect against attacks, vulnerabilities, and threats on this layer.

One critical best practice is to keep software and systems up-to-date with the latest security patches and updates. This ensures that known vulnerabilities are fixed, making it harder for attackers to exploit them. It’s also important to regularly monitor systems and networks for signs of suspicious activity, such as unusual traffic patterns or login attempts.

Another best practice is to use secure protocols for data transmission and storage. Examples of secure protocols used at the Presentation Layer are Transport Layer Security (TLS) and Secure Sockets Layer (SSL), which encrypt communications between parties. Additionally, the use of robust encryption and decryption mechanisms, such as symmetric and asymmetric key encryption, can help protect against man-in-the-middle and replay attacks.

Enforcing strict access controls and implementing a solid data classification system can also secure the presentation layer. This includes access controls to limit who can view, modify or delete sensitive data and a data classification system which can help determine how data is handled, processed and protected.

Implementing a robust incident response plan that includes detailed procedures for identifying, containing and reporting security incidents can also be a valuable asset in case of a security breach. It’s also important to regularly train employees on security best practices and to make them aware of the importance of security in the presentation layer.

In addition, performing regular penetration testing, Vulnerability Assessments, and security audits can also help to identify and address security vulnerabilities. This can include testing the effectiveness of encryption and decryption mechanisms, evaluating the robustness of access controls, and identifying potential vulnerabilities in data format translation and compression/decompression mechanisms.

7. Conclusion

In conclusion, the presentation layer in the OSI model is a critical component in the data transmission process. Its functions include data format translation, data compression and decompression, and encryption and decryption. These functions are vital to ensure that the data is in a format compatible with the application layer and to protect the data during transmission.

We have discussed how the presentation layer plays a vital role in the OSI model. The techniques and technologies used in the presentation layer to perform data format translation, compression and decompression, encryption and decryption. The article also includes the advantages and disadvantages of each technique, real-life examples and case studies, if applicable, that illustrate the concepts and makes them more relatable.

The topic of the presentation layer in the OSI model is essential for anyone working in the network security and communications field, as it provides an understanding of how data is protected and formatted during transmission. We hope this article has provided a comprehensive understanding of the role and functions of the presentation layer in the OSI model.

However, it’s important to note that the Presentation Layer, like any other layer in the OSI model, is also vulnerable to various attacks, vulnerabilities, and threats. Therefore, it is crucial to implement security best practices to protect against these threats, such as keeping software and systems up-to-date with the latest security patches and updates, using secure protocols, and robust encryption and decryption mechanisms. Strict access controls, incident response plans, and regular security assessments can also help secure the Presentation Layer.

8. FAQs on the Presentation Layer

• How does the presentation layer ensure data format compatibility?

The presentation layer ensures data format compatibility by providing a set of protocols and standards for data representation and encoding. These protocols, such as ASCII or Unicode, define a standard format for data so that it can be easily understood and processed by different systems. This helps to ensure that data can be exchanged between other systems without loss of meaning or integrity.

• How does the presentation layer protect data during transmission?

The presentation layer protects data during transmission by using various encryption techniques to ensure that the data is secure as it is transmitted over a network. Encryption is the process of converting plaintext data into a coded format (ciphertext) unreadable by unauthorised parties. Standard encryption methods used at the presentation layer include SSL (Secure Sockets Layer) and TLS (Transport Layer Security).

• What are some standard encryption algorithms used in the presentation layer?

Some standard encryption algorithms used in the presentation layer include:

• RSA (Rivest-Shamir-Adleman)
• AES (Advanced Encryption Standard)
• DES (Data Encryption Standard)
• 3DES (Triple Data Encryption Standard)
• What is the difference between symmetric and asymmetric encryption in the presentation layer?

Symmetric key encryption and asymmetric key encryption are both encryption methods that are used to protect data during transmission, but they use different techniques to secure the data.

Symmetric key encryption uses a single shared key for encryption and decryption, meaning that the sender and receiver both have to use the same key to encrypt and decrypt the data.

Asymmetric key encryption, also called public-key encryption, uses a pair of keys, one for encryption (the public key) and one for decryption (the private key). So the sender uses the recipient’s public key to encrypt the data, and the recipient uses their private key to decrypt the data.

• How does the presentation layer handle data format translation for different data types?

The presentation layer handles data format translation for different data types using a set of protocols and standards for data representation and encoding. These protocols, such as ASCII or Unicode, define a standard format for data so that it can be easily understood and processed by different systems. The presentation layer can also use data conversion algorithms to convert data between other formats, such as a Word document to a PDF.

• How does the presentation layer interact with other layers in the OSI model?

The presentation layer, the sixth layer in the OSI model, acts as an intermediary between the application layer (layer 7) and the session layer (layer 5). It is responsible for translating data between different formats and encoding schemes, and it is also responsible for compressing and decompressing data. The presentation layer communicates with the application layer to convert the data it receives into a format the application can understand. It also communicates with the session layer to establish, manage, and terminate sessions between networked devices.

• How do changes in data formats affect the presentation layer?

Changes in data formats can have a significant impact on the presentation layer, as the presentation layer is responsible for converting data between different formats. The presentation layer must be updated when data formats change to support the new design. If this is done, the presentation layer can convert the data, which may be unreadable or lost. Additionally, there are changes in the protocol or standard used in the presentation layer. In that case, it will affect the compatibility with other systems, so the sending and receiving ends have to use the same protocol. Otherwise, they would not be able to understand each other.

• How does the presentation layer handle data compression and decompression in real-time communications?

The presentation layer is responsible for compressing and decompressing data in real-time communications. Compression reduces data size to improve transmission efficiency, while decompression restores the data to its original format. The presentation layer uses various compression algorithms to compress data and the same algorithms to decompress the data when it is received.

In real-time communications, the presentation layer might use lossless compression algorithms to compress the data in order not to lose any information but at the same time still be able to compress the data to a smaller size.

• How can data integrity be maintained in the presentation layer?

Data integrity in the presentation layer can be maintained using encryption, secure hash algorithms, and error-detection codes.

Encryption is the process of converting plaintext data into a coded format (ciphertext) that is unreadable by unauthorised parties. This helps to protect data from unauthorised access and modification during transmission.

Secure hash algorithms are used to create a unique digital signature for each piece of data, which can be used to verify the integrity of the data upon receipt. This helps to detect any changes or modifications that may have occurred during transmission.

Error-detection codes are used to detect errors in the data during transmission and can help to correct these errors.

Additionally, the presentation layer can also use a digital signature or digital certificate to ensure the authenticity of data, which is the process of using a digital signature to ensure that the data is not tampered with during transmission.

• Stack Overflow for Teams Where developers & technologists share private knowledge with coworkers
• Advertising & Talent Reach devs & technologists worldwide about your product, service or employer brand
• OverflowAI GenAI features for Teams
• OverflowAPI Train & fine-tune LLMs
• Labs The future of collective knowledge sharing
• About the company Visit the blog

Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

Get early access and see previews of new features.

OSI model - What's the presentation and session layer for?

So I feel I pretty well understand the application layer, and everything below (and including) the transport layer.

The session and presentation layers, though, I don't fully understand. I've read the simplistic descriptions in Wikipedia, but it doesn't have an example of why separating out those layers is useful.

• What is the session layer? What does it do, and under what circumstances is it better to have a session layer than simply talk to the transport with your app?
• What is the presentation layer? (same questions as above)

7 Answers 7

The session layer is meant to store states between two connections, like what we use cookies for when working with web programming.

The presentation layer is meant to convert between different formats. This was simpler when the only format that was worried about was character encoding, ie ASCII and EBCDIC. When you consider all of the different formats that we have today(Quicktime, Flash, Pdf) centralizing this layer is out of the question.

TCP/IP doesn't make any allocation to these layers, since they are really out of the scope of a networking protocol. It's up to the applications that take advantage of the stack to implement these.

The reasons there aren't any examples on wikipedia is that there aren't a whole lot of examples of the OSI network model, period.

OSI has once again created a standard nobody uses, so nobody really know how one should use it.

Layers 5-6 are not commonly used in today's web applications, so you don't hear much about them. The TCP/IP stack is slightly different than a pure OSI Model.

One of the reasons TCP/IP is used today instead of OSI is it was too bloated and theoretical, the session and presentation layer aren't really needed as separate layers as it turned out.

I think that presentation layer protocols define the format of data. This means protocols like XML or ASN.1. You could argue that video/audio codecs are part of the presentation layer Although this is probably heading towards the application layer.

I can't help you with the session layer. That has always baffled me.

To be honest, there are very vague boundaries in everything above the transport layer. This is because it is usually handled by a single software application. Also, these layers are not directly associated with transporting data from A to B. Layers 4 and below each have a very specific purpose in moving the data e.g. switching, routing, ensuring data integrity etc. This makes it easier to distinguish between these layers.

Presentation Layer The Presentation Layer represents the area that is independent of data representation at the application layer - in general, it represents the preparation or translation of application format to network format, or from network formatting to application format. In other words, the layer “presents” data for the application or the network. A good example of this is encryption and decryption of data for secure transmission - this happens at Layer 6.

Session Layer When two devices, computers or servers need to “speak” with one another, a session needs to be created, and this is done at the Session Layer. Functions at this layer involve setup, coordination (how long should a system wait for a response, for example) and termination between the applications at each end of the session.

For the presentation layer :because most of communication done between heterogeneous systems (Operating Systems,programing langages,cpu architectures)we need to use a unified idepedent specification .like ANS1 ans BRE.

Your Answer

Reminder: Answers generated by artificial intelligence tools are not allowed on Stack Overflow. Learn more

Sign up or log in

Post as a guest.

Required, but never shown

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy .

Not the answer you're looking for? Browse other questions tagged networking model stack osi or ask your own question .

• The Overflow Blog
• The hidden cost of speed
• The creator of Jenkins discusses CI/CD and balancing business with open source
• Featured on Meta
• Announcing a change to the data-dump process
• Bringing clarity to status tag usage on meta sites
• What does a new user need in a homepage experience on Stack Overflow?
• Feedback requested: How do you use tag hover descriptions for curating and do...
• Staging Ground Reviewer Motivation

Hot Network Questions

• Minimal permutation degree of the dihedral group
• Can the planet Neptune be seen from Earth with binoculars?
• Is there a way to read lawyers arguments in various trials?
• Is this host and 'parasite' interaction feasible?
• How to extrude a profile along multiple curves keeping tilt equal between instances and sane normals?
• Information theoretical interpretation of Free Energy
• Romeo & Juliet laws and age of consent laws
• Starting with 2014 "+" signs and 2015 "−" signs, you delete signs until one remains. What’s left?
• What prevents random software installation popups from mis-interpreting our consents
• The head of a screw is missing on one side of the spigot outdoor
• Book Request: Machshava by Topics
• Were the common people in Germany ("good germans") morally co-responsible of the war crimes of their government?
• Could they free up a docking port on ISS by undocking the emergency vehicle and letting it float next to the station for a little while
• Can anyone debunk this claim regarding Non Hindus and other religion as per Hindu scriptures
• How can we know how good a TRNG is?
• How to truncate text in latex?
• Is the 2024 Ukrainian invasion of the Kursk region the first time since WW2 Russia was invaded?
• Has anyone returned from space in a different vehicle from the one they went up in? And if so who was the first?
• Can you move between an attack and the attack granted by Horde Breaker?
• What is the optimal number of function evaluations?
• Beatles reference in parody story from the 1980s
• Are others allowed to use my copyrighted figures in theses, without asking?
• Parsing and processing "resolvectl statistics" output using awk
• 70s-90s Anime Mecha Movie/Series

Presentation Domain Data Layering

26 August 2015

Martin Fowler

team organization

encapsulation

application architecture

web development

One of the most common ways to modularize an information-rich program is to separate it into three broad layers: presentation (UI), domain logic (aka business logic), and data access. So you often see web applications divided into a web layer that knows about handling HTTP requests and rendering HTML, a business logic layer that contains validations and calculations, and a data access layer that sorts out how to manage persistent data in a database or remote services.

On the whole I've found this to be an effective form of modularization for many applications and one that I regularly use and encourage. It's biggest advantage (for me) is that it allows me to reduce the scope of my attention by allowing me to think about the three topics relatively independently. When I'm working on domain logic code I can mostly ignore the UI and treat any interaction with data sources as an abstract set of functions that give me the data I need and update it as I wish. When I'm working on the data access layer I focus on the details of wrangling the data into the form required by my interface. When I'm working on the presentation I can focus on the UI behavior, treating any data to display or update as magically appearing by function calls. By separating these elements I narrow the scope of my thinking in each piece, which makes it easier for me to follow what I need to do.

This narrowing of scope doesn't imply any sequence to programming them - I usually find I need to iterate between the layers. I might build the data and domain layers off my initial understanding of the UX, but when refining the UX I need to change the domain which necessitates a change to the data layer. But even with that kind of cross-layer iteration, I find it easier to focus on one layer at a time as I make changes. It's similar to the switching of thinking modes you get with refactoring's two hats .

Another reason to modularize is to allow me to substitute different implementations of modules. This separation allows me to build multiple presentations on top of the same domain logic without duplicating it. Multiple presentations could be separate pages in a web app, having a web app plus mobile native apps, an API for scripting purposes, or even an old fashioned command line interface. Modularizing the data source allows me to cope gracefully with a change in database technology, or to support services for persistence that may change with little notice. However I have to mention that while I often hear about data access substitution being a driver for separating the data source layer, I rarely hear of someone actually doing it.

Modularity also supports testability, which naturally appeals to me as a big fan of SelfTestingCode . Module boundaries expose seams that are good affordance for testing . UI code is often tricky to test, so it's good to get as much logic as you can into a domain layer which is easily tested without having to do gymnastics to access the program through a UI 1 . Data access is often slow and awkward, so using TestDoubles around the data layer often makes domain logic testing much easier and responsive.

1: A PageObject is also an important tool to help testing around UIs.

While substitutability and testability are certainly benefits of this layering, I must stress that even without either of these reasons I would still divide into layers like this. The reduced scope of attention reason is sufficient on its own.

When talking about this we can either look at it as one pattern (presentation-domain-data) or split it into two patterns (presentation-domain, and domain-data). Both points of view are useful - I think of presentation-domain-data as a composite of presentation-domain and domain-data.

I consider these layers to be a form of module, which is a generic word I use for how we clump our software into relatively independent pieces. Exactly how this corresponds to code depends on the programming environment we're in. Usually the lowest level is some form of subroutine or function. An object-oriented language will have a notion of class that collects functions and data structure. Most languages have some form of higher level called packages or namespaces, which often can be formed into a hierarchy. Modules may correspond to separately deployable units: libraries, or services, but they don't have to.

Layering can occur at any of these levels. A small program may just put separate functions for the layers into different files. A larger system may have layers corresponding to namespaces with many classes in each.

I've mentioned three layers here, but it's common to see architectures with more than three layers. A common variation is to put a service layer between the domain and presentation, or to split the presentation layer into separate layers with something like Presentation Model . I don't find that more layers breaks the essential pattern, since the core separations still remain.

The dependencies generally run from top to bottom through the layer stack: presentation depends on the domain, which then depends on the data source. A common variation is to arrange things so that the domain does not depend on its data sources by introducing a mapper between the domain and data source layers. This approach is often referred to as a Hexagonal Architecture .

These layers are logical layers not physical tiers. I can run all three layers on my laptop, I can run the presentation and domain model in a desktop with a database on a server, I can split the presentation with a rich client in the browser and a Backed For Frontend on the server. In that case I treat the BFF as a presentation layer as it's focused on supporting a particular presentation option.

Although presentation-domain-data separation is a common approach, it should only be applied at a relatively small granularity. As an application grows, each layer can get sufficiently complex on its own that you need to modularize further. When this happens it's usually not best to use presentation-domain-data as the higher level of modules. Often frameworks encourage you to have something like view-model-data as the top level namespaces; that's OK for smaller systems, but once any of these layers gets too big you should split your top level into domain oriented modules which are internally layered.

Developers don't have to be full-stack but teams should be.

One common way I've seen this layering lead organizations astray is the AntiPattern of separating development teams by these layers. This looks appealing because front-end and back-end development require different frameworks (or even languages) making it easy for developers to specialize in one or the other. Putting those people with common skills together supports skill sharing and allows the organization to treat the team as a provider of a single, well-delineated type of work. In the same way, putting all the database specialists together fits in with the common centralization of databases and schemas. But the rich interplay between these layers necessitates frequent swapping between them. This isn't too hard when you have specialists in the same team who can casually collaborate, but team boundaries add considerable friction, as well as reducing an individual's motivation to develop the important cross-layer understanding of a system. Worse, separating the layers into teams adds distance between developers and users. Developers don't have to be full-stack (although that is laudable) but teams should be.

Further Reading

I've written about this separation from a number of different angles elsewhere. This layering drives the structure of P of EAA and chapter 1 of that book talks more about this layering. I didn't make this layering a pattern in its own right in that book but have toyed with that territory with Separated Presentation and PresentationDomainSeparation .

For more on why presentation-domain-data shouldn't be the highest level modules in a larger system, take a look at the writing and speaking of Simon Brown . I also agree with him that software architecture should be embedded in code.

I had a fascinating discussion with my colleague Badri Janakiraman about the nature of hexagonal architectures. The context was mostly around applications using Ruby on Rails, but much of the thinking applies to other cases when you may be considering this approach.

Acknowledgements