|
|
Please use this identifier to cite or link to this item:
https://repositorio.utn.edu.ec/handle/123456789/19674Full metadata record
| DC Field | Value | Language |
|---|---|---|
| dc.contributor.author | Quiña-Mera, Antonio | - |
| dc.contributor.author | García, José María | - |
| dc.contributor.author | Fernández, Pablo | - |
| dc.contributor.author | Vega Molina, Pablo | - |
| dc.contributor.author | Ruiz Cortés, Antonio | - |
| dc.date.accessioned | 2026-04-28T21:34:44Z | - |
| dc.date.available | 2026-04-28T21:34:44Z | - |
| dc.date.issued | 2026-04-28 | - |
| dc.identifier.issn | 1865-0929 | - |
| dc.identifier.uri | https://repositorio.utn.edu.ec/handle/123456789/19674 | - |
| dc.description.abstract | Actualmente, GraphQL se ha consolidado como un lenguaje de consulta para el desarrollo de API web que busca mejorar diversos problemas de acceso a datos en las API RESTful. El presente trabajo tiene como objetivo estudiar los efectos en la calidad del software de las API desarrolladas con arquitecturas REST y GraphQL, consumidas desde aplicaciones móviles. Para ello, diseñamos un experimento computacional que compara la característica de calidad "eficiencia de rendimiento" del consumo de aplicaciones móviles a tres API: una API GraphQL y dos API REST (una que expone consultas complejas en varios endpoints y la otra que expone consultas complejas en un único endpoint). Los resultados muestran que la calidad del software de la API desarrollada con arquitectura GraphQL es superior a la de la desarrollada con arquitectura REST. | es_EC |
| dc.language.iso | spa | es_EC |
| dc.publisher | Springer Nature Link | es_EC |
| dc.rights | openAccess | es_EC |
| dc.rights | Atribución-NoComercial-CompartirIgual 3.0 Ecuador | * |
| dc.rights.uri | http://creativecommons.org/licenses/by-nc-sa/3.0/ec/ | * |
| dc.subject | LENGUAJE | es_EC |
| dc.subject | DESARROLLO | es_EC |
| dc.subject | PROBLEMAS | es_EC |
| dc.subject | DATOS | es_EC |
| dc.title | GraphQL o REST para aplicaciones móviles | es_EC |
| dc.type | Article | es_EC |
| dc.description.degree | N/A | es_EC |
| dc.coverage | Ibarra. Ecuador | es_EC |
| dc.contributor.orcid | https://orcid.org/0000-0003-2516-9016 | es_EC |
| dc.contributor.orcid | https://orcid.org/0000-0002-0303-2740 | es_EC |
| dc.contributor.orcid | https://orcid.org/0000-0002-8763-0819 | es_EC |
| dc.title.en | GraphQL or REST for mobile applications | es_EC |
| dc.subject.en | LANGUAGE | es_EC |
| dc.subject.en | DEVELOPMENT | es_EC |
| dc.subject.en | PROBLEMS | es_EC |
| dc.subject.en | DATA | es_EC |
| dc.description.abstract-en | Currently, GraphQL has emerged as a query language for developing web APIs that propose to improve several data access problems of RESTful APIs. The present paper aims to study the effects on software quality of APIs developed with REST and GraphQL architectures consumed from mobile applications. For this, we design a computational experiment that compares the quality characteristic “performance efficiency" of mobile application consumption to three APIs; one GraphQL API and two REST APIs (one exposes complex queries on several endpoints, the other exposes complex queries on a single endpoint). The results show that the software quality of the API developed with GraphQL architecture is higher than that developed with REST architecture. | es_EC |
| dc.identifier.doi | https://link.springer.com/chapter/10.1007/978-3-031-20319-0_2 | es_EC |
| Appears in Collections: | Artículos | |
Files in This Item:
There are no files associated with this item.
This item is protected by original copyright |
This item is licensed under a Creative Commons License
