2018 2nd East Indonesia Conference on Computer and Information Technology (EIConCIT) 2018
DOI: 10.1109/eiconcit.2018.8878524
|View full text |Cite
|
Sign up to set email alerts
|

Performance Analysis of GraphQL and RESTful in SIM LP2M of the Hasanuddin University

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
8
0
3

Year Published

2020
2020
2023
2023

Publication Types

Select...
5
2
1
1

Relationship

1
8

Authors

Journals

citations
Cited by 12 publications
(11 citation statements)
references
References 3 publications
0
8
0
3
Order By: Relevance
“…GraphQL that uses a single endpoint is more efficient than other APIs that use multiple endpoints, but GraphQL will also be a bit slower to query complex databases and have many relationships in addition to that other APIs are built with multiple endpoints to determine the data returned. This will increase the number of client-server calls to display data to the user and this may result in poorer service performance in Application requirements (Hartina et al, 2018).…”
Section: Graph Query Language (Graphq)mentioning
confidence: 99%
“…GraphQL that uses a single endpoint is more efficient than other APIs that use multiple endpoints, but GraphQL will also be a bit slower to query complex databases and have many relationships in addition to that other APIs are built with multiple endpoints to determine the data returned. This will increase the number of client-server calls to display data to the user and this may result in poorer service performance in Application requirements (Hartina et al, 2018).…”
Section: Graph Query Language (Graphq)mentioning
confidence: 99%
“…Penelitian lain membahas mengenai perbandingan performa antara GraphQL dan REST API pada sistem informasi, penelitian tersebut menyimpulkan bahwa GraphQL dapat menjadi pilihan yang tepat ketika data yang dibutuhkan sering berubah (Hartina, Lawi, & Panggabean, 2018).…”
Section: Pendahuluanunclassified
“…The REST configuration creates a complicated situation whenever there is a change on the back-end, it will cause an adjustment to the front-end to query the exact endpoint for the desired resource. On the other hand, GraphQL will take some time when the request is handled at a single endpoint to find the right resource [1,3,12,13,16]. Figure 3 illustrates the difference between REST and GraphQL architecture.…”
Section: Architectural Difference Of Rest and Graphqlmentioning
confidence: 99%
“…Meanwhile, web service workload performance is more easily demonstrated through CPU load and memory usage. Obviously, the response time and throughput depend on the workload the web server is experiencing at the time [12,14,16,21]. Therefore, this paper evaluates 4 basic performance measures that clearly distinguish the two technologies based on their natural purpose.…”
Section: Performance Measurementsmentioning
confidence: 99%