On the other hand, the great majority of computer systems employ fewer levels than what the OSI model specifies. This is true because of the way computer systems are constructed. Why not apply less ayers than what you do now? What potential drawbacks may there be from using fewer layers?

On the other hand, the great majority of computer systems employ fewer levels than what the OSI model specifies. This is true because of the way computer systems are constructed. Why not apply less ayers than what you do now? What potential drawbacks may there be from using fewer layers?

Database System Concepts

7th Edition

ISBN:9780078022159

Author:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan

Publisher:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan

Chapter1: Introduction

Section: Chapter Questions

Problem 1PE

See similar textbooks

Similar questions

Is there a distinction to be made between the term "interdependence" and other notions used in system theories, and how does it differ from them?
However, most computer systems employ fewer layers than is recommended by the OSI model. The design of computers makes this inevitable. Why not use fewer layers? I was wondering what some of the potential drawbacks might be if fewer layers were used.
However, the OSI model's recommended number of layers is more than what is often used in computer systems. The design of computers makes this inevitable. I think you may benefit from utilizing less layers. I was wondering what some of the possible negatives may be if a smaller number of layers were used.
Most real-world computer systems don't follow the OSI model's layer count. Current conditions are due to computer system fundamentals. Use less product if you can. What's wrong with fewer layers?
Contrarily, the OSI model proposes more layers than are actually used in most modern computer systems. When doing so, try to minimize the number of layers. Does reducing the number of layers have any drawbacks?
The following is a definition of the layered approach to operating system architecture: In what respects does this strategy function and where does it fall short? Why not use an image to explain your point?
Most current computer systems use fewer OSI model tiers. Computing systems' nature causes this. Drop some layers? Do fewer organisational levels have any drawbacks?
Yet, most practical computer systems do not have as many levels as the OSI model suggests. This is due of a feature built into computers themselves. Keep the level count as low as possible. Is there anything we need to worry about if we cut down on the overall number of layers?
However, the OSI model's recommended seven levels are more than most computer systems employ. Isn't it better to reduce the amount of layers? I was wondering if there were any drawbacks to use fewer layers.
In the realm of computer architecture, time-sharing systems and distributed systems exhibit distinct characteristics that set them apart from one another. Could you please provide a comparison and contrast between the two entities?
Nevertheless, the OSI model's recommended number of layers is more than what is often used in computer systems. Due to the nature of computing, this is the case. To simplify things, why not use fewer layers? I was wondering what some of the possible negatives may be if fewer layers were used.
On the other hand, the majority of computer systems do not use as many layers as the OSI model implies they should. If it's at all feasible, try to cut down on the number of layers. Is there a drawback to using a lower number of layers?