human: Given a node-centered hypergraph: <hypergraph>, where nodes represent authors and hyperedges represent groups of authors who co-authored the same paper.

Details of the hypergraph:
Center node: "Performance of graph query languages: comparison of cypher, gremlin and native access in Neo4j"
  Abstract: NoSQL and especially graph databases are constantly gaining popularity among developers of Web 2.0 applications as they promise to deliver superior performance when handling highly interconnected data compared to traditional relational databases.  Apache Shindig  is the reference implementation for  OpenSocial  with its highly interconnected data model. However, the default back-end is based on a relational database. In this paper we describe our experiences with a different back-end based on the graph database  Neo4j  and compare the alternatives for querying data with each other and the  JPA -based sample back-end running on  MySQL . Moreover, we analyze why the different approaches often may yield such diverging results concerning throughput. The results show that the graph-based back-end can match and even outperform the traditional  JPA  implementation and that  Cypher  is a promising candidate for a standard graph query language, but still leaves room for improvements.

Connected through hyperedge HE-1 (induced by source paper "Mogwaï: A framework to handle complex queries on large models"):
  with members:
    - "Extending Complex Event Processing to Graph-structured Information"

Connected through hyperedge HE-2 (induced by source paper "Relational database: a practical foundation for productivity"):
  with members:
    - "A foundation of CODD's relational maybe-operations"
    - "Query by example"
    - "Human Factors Studies of Database Query Languages: A Survey and Assessment"

Question: Please tell me which research area the center author belongs to. The 4 classes are: Computer science, Mathematics, Engineering, Economics, Psychology, Business. Directly output the class name.

gpt: Computer science