Oracle Network Independence

Network protocols should not be an issue for distributed databases. Protocol conversion routines such as Net8 permit synchronous channels (such as those on IBM mainframes) to communicate with the asynchronous UNIX world.
They also accommodate differences in topology so that LU6.2^[1] can communicate with TCP/IP, and so on.

It is important to distinguish between distributed and decentralized databases. A decentralized database is also stored on computers at multiple locations. However, the computers are not interconnected by network and database software that make the data appear to be in one logical database. Thus, users at the various sites cannot share data. A decentralized database is best regarded as a collection of independent databases, rather than having the geographical distribution of a single database.

Systems Engineering is an interdisciplinary approach and means for enabling the realization and deployment of successful systems. It can be viewed as the application of engineering techniques to the engineering of systems, as well as the application of a systems approach to engineering efforts. Systems Engineering integrates other disciplines and specialty groups into a team effort, forming a structured development process that proceeds from concept to production to operation and disposal. Systems Engineering considers both the business and the technical needs of all customers, with the goal of providing a quality product that meets the user needs.
Network protocols should not be an issue for distributed databases. Protocol conversion routines such as Net8 allow synchronous channels (such as those on IBM mainframes) to communicate with asynchronous Unix. They also accommodate differences in topology so that LU6.2 (Logical Unit 6.2 is an IBM-originated communications protocol specification dating from 1974, and is part of IBM's Systems Network Architecture) can communicate with TCP/IP.

[1]LU6.2 Logical Unit 6.2 is an IBM-originated communications protocol specification dating from 1974 and is part of IBM's (SNA) Systems Network Architecture.