Group:
distributed database
Topic:
broadcasting information
Topic:
client-server model for distributed systems
Topic:
communication port
Topic:
communication protocols
Topic:
computational mail
Topic:
computer architecture
Topic:
concurrency control by sequencers
Topic:
data parallel processing
Topic:
database implementation
Topic:
database security
Topic:
defining a process
Topic:
distributed system security
Topic:
examples of distributed systems and applications
Topic:
extensible systems
Topic:
hardware for interprocess communication
Topic:
hypertext as a distributed system
Topic:
implementation of hypertext databases
Topic:
interprocess communication
Topic:
message queues for communication
Topic:
mobile code
Topic:
multiple processors
Topic:
parameter passing by message
Topic:
process migration
Topic:
reliable broadcast
Topic:
reliable communication
Topic:
reliability of distributed systems
Topic:
remote procedure call
Topic:
routing electronic mailing
Topic:
security of remotely executed code
Topic:
semistructured messages for automated processing
Topic:
sending an object across a network
Topic:
software maintenance and testing of distributed systems
Topic:
specification and design of distributed systems
Topic:
timestamps
Topic:
translation of data
Topic:
updating information in a distributed system
| |
Subtopic: performance requirements 
| Quote: differing performance requirements for centralized vs. distributed systems; e.g., compare idle locomotives with idle cars [»liskB10_1981]
|
Subtopic: client/server
| Quote: implement distributed systems via servers and clients on a local area network; clients request services from servers [»shriS7_1982]
|
Subtopic: service orientation
| Quote: Amazon constructs its gateway page from over a 100 services; each service conceived, built, and operated by a team [»grayJ5_2006]
| | Quote: prohibit database access by clients; simplifies scaling and reliability updates of services [»grayJ5_2006]
|
Subtopic: clusters
| Quote: a Google query touches 100s Mbytes of data and execute billions of CPU cycles [»barrLA3_2003]
| | Quote: Google runs more than 15,000 commodity-class PCs
| | Quote: energy efficiency and price-performance are the primary factors for Google clusters
|
Subtopic: load balancing
| Quote: better load balancing if randomly chose two machines and pick the less loaded [»mitzM5_2002]
|
Subtopic: unify local/remote
| Quote: the Styx communication protocol unifies local and remote resources
| | Quote: Inferno provides a complete operating system with identical, distributed applications on a wide variety of machines [»dorwSM1_1997]
|
Subtopic: shared type system
| Quote: a shared type system is necessary to integrate multiple languages [»hamiJ2_2003]
|
Subtopic: external data format
| Quote: an external data format should be self-describing and preserved under round-tripping; e.g., Lisp S-expressions [»simeJ1_2003]
|
Subtopic: distributed component
| Quote: a Jini network allows membership changes and communication changes between components; long-running [»waldJ7_1999]
| | Quote: a Jini component offers a resource via a lease for a specific period of time; may be cancelled by client or renewed by client and server [»waldJ7_1999]
|
Subtopic: broadcast
| Quote: use broadcast methods to turn mono-process into distributed programs [»stefM1_1987]
| | Quote: a distributed system needs to deal with groups of entities as well as individual ones [»cherDR3_1988]
| | Quote: Clearinghouse stubs must use broadcast to locate a server that's moved [»oppeDC7_1983]
| | Quote: an Amoeba domain is an interconnected collection of local area networks; broadcasts to every machine in the domain but none outside; e.g., for locating a port [»taneAS12_1990]
|
Subtopic: network distance
| Quote: from the GFS network topology, estimate distance by IP addresses
|
Subtopic: heartbeat coordination
| Quote: a single GFS master manages the file system metadata for chunkservers; e.g., namespace, access control, mappings, garbage collection [»gherS10_2003]
| | Quote: use heartbeat messages for communication between master and chunkservers
| | Quote: heartbeat messages sync chunkservers and master incrementally; deletes orphaned chunks
|
Subtopic: distributed naming
| Quote: REST manipulates resources and concepts by transferring representations using a resource identifier and generic interface; allows independent authoring across multiple trust domains [»fielRT5_2002]
| | Quote: use intentional names in distributed environments that describe what is needed instead of where to find it [»adjiW12_1999]
| | Quote: the Intentional Naming System (INS) uses a hierarchy of attributes to locate services and route messages to the appropriate end-nodes [»adjiW12_1999]
|
Subtopic: optimizing data communication
| Quote: chunkservers forward data immediately to the next replica over a precomputed path [»gherS10_2003]
|
Subtopic: distributed consistency
| Quote: optimal distributed algorithm for identifying corrupted files by exchanging page signatures [»abdeKA1_1994]
|
Subtopic: distributed priority
| Quote: the priority ceiling protocol may be extended to distributed systems [»rajkR_1991]
|
Subtopic: distributed timers
| Quote: use hashed and hierarchical timing wheels for constant time maintenance of timers; practical for thousands of active timers [»vargG12_1997]
|
Subtopic: distributed scripting
| Quote: REBOL is a scripting language for distributed applications; datatypes include e-mail, money, URLs [»sassC7_2000]
|
Subtopic: future values
| Quote: use futures for concurrent return values, event objects, and macro-dataflow programming; wait until value is assigned; assign-once [»chriTW2_2002]
|
Subtopic: disconnected operation
| Quote: can run disconnected from a network if cache data; allows one to two day disconnections; update afterwards in a minute [»kistJJ2_1992]
|
Subtopic: membership
| Quote: membership is difficult for epidemic algorithms; e.g., broadcasting partial membership has problems with uniformity, adaptivity, and bootstrapping [»eugsPT5_2004]
|
Subtopic: software module registry
| Quote: maintain a distributed system with a global registry of software modules; unique identifier for name, version, security interface, and performance parameters; modules exchange ids [»fedaA3_1997]
|
Subtopic: Unix networking
| Quote: Unix network by a spool directory containing work to be done; after logging in to the remote machine, the uucico programs agree on protocols [»nowiDA8_1978]
| | Quote: exchange checksums to avoid copying large amounts of usually identical data [»nowiDA8_1978]
| | Quote: once the Unix network was in use, system maintainers were easily persuaded to keep it running and improve throughput [»nowiDA8_1978]
|
Subtopic: automated logins
| Quote: implement an information network by automatic login using Unix [»gammR_1982]
| | Quote: implemented distributed system by automated logins working like a postman [»gammR_1982]
| | Quote: enter farmer's data sheets into personal computers with automatic processing at remote sites [»gammR_1982]
| | Quote: implement rural information network by a few computers with interactive protocol interpreters [»gammR_1982]
|
Related Topics
Group: distributed database (6 topics, 194 quotes)
Topic: broadcasting information (18 items)
Topic: client-server model for distributed systems (25 items)
Topic: communication port (40 items)
Topic: communication protocols (62 items)
Topic: computational mail (11 items)
Topic: computer architecture (46 items)
Topic: concurrency control by sequencers (27 items)
Topic: data parallel processing (14 items)
Topic: database implementation (18 items)
Topic: database security (12 items)
Topic: defining a process (23 items)
Topic: distributed system security (17 items)
Topic: examples of distributed systems and applications (25 items)
Topic: extensible systems (22 items)
Topic: hardware for interprocess communication (31 items)
Topic: hypertext as a distributed system (4 items)
Topic: implementation of hypertext databases (17 items)
Topic: interprocess communication (29 items)
Topic: message queues for communication (36 items)
Topic: mobile code (14 items)
Topic: multiple processors (10 items)
Topic: parameter passing by message (31 items)
Topic: process migration (3 items)
Topic: reliable broadcast (29 items)
Topic: reliable communication (29 items)
Topic: reliability of distributed systems (35 items)
Topic: remote procedure call (44 items)
Topic: routing electronic mailing (12 items)
Topic: security of remotely executed code (24 items)
Topic: semistructured messages for automated processing (22 items)
Topic: sending an object across a network (11 items)
Topic: software maintenance and testing of distributed systems (16 items)
Topic: specification and design of distributed systems (14 items)
Topic: timestamps (19 items)
Topic: translation of data (26 items)
Topic: updating information in a distributed system
(50 items)
|
