human: Given a node-centered hypergraph: <hypergraph>, where nodes represent papers and hyperedges represent sets of papers co-cited by a source paper.

Details of the hypergraph:
Center node: "building on quicksand"
  Abstract: Reliable systems have always been built out of unreliable components. Early on, the reliable components were small such as mirrored disks or ECC (Error Correcting Codes) in core memory. These systems were designed such that failures of these small components were transparent to the application. Later, the size of the unreliable components grew larger and semantic challenges crept into the application when failures occurred. #R##N#As the granularity of the unreliable component grows, the latency to communicate with a backup becomes unpalatable. This leads to a more relaxed model for fault tolerance. The primary system will acknowledge the work request and its actions without waiting to ensure that the backup is notified of the work. This improves the responsiveness of the system. #R##N#There are two implications of asynchronous state capture: 1) Everything promised by the primary is probabilistic. There is always a chance that an untimely failure shortly after the promise results in a backup proceeding without knowledge of the commitment. Hence, nothing is guaranteed! 2) Applications must ensure eventual consistency. Since work may be stuck in the primary after a failure and reappear later, the processing order for work cannot be guaranteed. #R##N#Platform designers are struggling to make this easier for their applications. Emerging patterns of eventual consistency and probabilistic execution may soon yield a way for applications to express requirements for a "looser" form of consistency while providing availability in the face of ever larger failures. #R##N#This paper recounts portions of the evolution of these trends, attempts to show the patterns that span these changes, and talks about future directions as we continue to "build on quicksand".

Connected through hyperedge HE-1 (induced by source paper "cloudburst stateful functions as a service"):
  with members:
    - "cloud programming simplified a berkeley view on serverless computing"
    - "serverless computing one step forward two steps back"
    - "pretzel opening the black box of machine learning prediction serving systems"
    - "numpywren serverless linear algebra"
    - "ray a distributed framework for emerging ai applications"
    - "occupy the cloud distributed computing for the 99"
    - "serverless computing current trends and open problems"
    - "mobilenets efficient convolutional neural networks for mobile vision applications"

Connected through hyperedge HE-2 (induced by source paper "keeping calm when distributed consistency is easy"):
  with members:
    - "dissipation of stop and go waves via control of autonomous vehicles field experiments"
    - "blazes coordination analysis for distributed programs"
    - "communication steps for parallel query processing"
    - "relational transducers for declarative networking"

Connected through hyperedge HE-3 (induced by source paper "usability squared principles for doing good systems research in robotics"):
  with members:
    - "experimenting with robotic intra logistics domains"
    - "analysis and observations from the first amazon picking challenge"
    - "probabilistically bounded staleness for practical partial quorums"

Connected through hyperedge HE-4 (induced by source paper "antidote sql relaxed when possible strict when necessary"):
  with members:
    - "the homeostasis protocol avoiding transaction coordination through program analysis"

Connected through hyperedge HE-5 (induced by source paper "serverless computing one step forward two steps back"):
  with members:
    - "occupy the cloud distributed computing for the 99"
    - "clipper a low latency online prediction serving system"
    - "relational transducers for declarative networking"

Connected through hyperedge HE-6 (induced by source paper "ipa invariant preserving applications for weakly consistent replicated databases"):
  with members:
    - "the homeostasis protocol avoiding transaction coordination through program analysis"
    - "blazes coordination analysis for distributed programs"

Connected through hyperedge HE-7 (induced by source paper "optimistic aborts for geo distributed transactions"):
  with members:
    - "paxos made switch y"
    - "merlin a language for provisioning network resources"

Connected through hyperedge HE-8 (induced by source paper "incremental consistency guarantees for replicated objects"):
  with members:
    - "probabilistically bounded staleness for practical partial quorums"

Question: Please tell me which class the center node belongs to. The 40 classes are: cs.NA(Numerical Analysis), cs.MM(Multimedia), cs.LO(Logic in Computer Science), cs.CY(Computers and Society), cs.CR(Cryptography and Security), cs.DC(Distributed, Parallel, and Cluster Computing), cs.HC(Human-Computer Interaction), cs.CE(Computational Engineering, Finance, and Science), cs.NI(Networking and Internet Architecture), cs.CC(Computational Complexity), cs.AI(Artificial Intelligence), cs.MA(Multiagent Systems), cs.GL(General Literature), cs.NE(Neural and Evolutionary Computing), cs.SC(Symbolic Computation), cs.AR(Hardware Architecture), cs.CV(Computer Vision and Pattern Recognition), cs.GR(Graphics), cs.ET(Emerging Technologies), cs.SY(Systems and Control), cs.CG(Computational Geometry), cs.OH(Other Computer Science), cs.PL(Programming Languages), cs.SE(Software Engineering), cs.LG(Machine Learning), cs.SD(Sound), cs.SI(Social and Information Networks), cs.RO(Robotics), cs.IT(Information Theory), cs.PF(Performance), cs.CL(Computation and Language), cs.IR(Information Retrieval), cs.MS(Mathematical Software), cs.FL(Formal Languages and Automata Theory), cs.DS(Data Structures and Algorithms), cs.OS(Operating Systems), cs.GT(Computer Science and Game Theory), cs.DB(Databases), cs.DL(Digital Libraries), cs.DM(Discrete Mathematics). Directly output the class name.

gpt: cs.DC(Distributed, Parallel, and Cluster Computing)