Challenges faced by distributed computing

The core of the distributed architecture is the ability to call methods on objects or communicate with services that reside in different processes or even on different computers. It looks like
It is not difficult, but you must solve many problems:
L how to instantiate a remote object?
L if you want to call methods on an existing object, how do you obtain references to this object?
L The network protocol only transmits byte streams without transmitting objects. How can I call a method through byte stream?
L How secure is it? Can everyone call methods on a remote object?
L most networks are inherently unreliable. What happens if the remote object cannot be accessed? If the remote object receives a method call
Unable to send response, what should I do?
L calling remote objects is much slower than calling local methods. Do you want to call remote methods asynchronously so that the remote object can continue to process requests locally?
Why?
There are countless problems. Fortunately, the features in. NET Framework solve most of these problems, allowing developers to create distributed applications. ProgramNot Required
Too many details. These features make remote calls almost transparent to programmers (at least at the syntax level ). However, there may be some frauds in this simplification.
Deception, because developers must understand some basic principles of remote communication before they can write powerful and efficient distributed applications. Distributed System Mode clusters are helpful for enabling
Developers make informed design decisions when implementing distributed applications.
Enable