Gleison Brito

Faculdade Farias Brito, Computação, Graduate Student

Followers

Following

Public Views

Alan Freeman

David Pierre Leibovitz

Carleton University

Steffen Boehm

University of Exeter

Armando Marques-Guedes

UNL - New University of Lisbon

Fabiano Fagundes

CEULP/ULBRA

Roshan Chitrakar

Nepal College of Information Technology

J.-C. Spender

Kozminski University

Lev Manovich

Graduate Center of the City University of New York

Vivianne Moreira

Universidade Federal do Paraná

Natasha Sophie Pereira

Centro Universitário de Anápolis

Interests

Uploads

Papers by Gleison Brito

REST vs GraphQL: A Controlled Experiment. (arXiv:2003.04761v1 [cs.SE])

arXiv Computer Science, Mar 11, 2020

GoCity: Code City for Go

2019 IEEE 26th International Conference on Software Analysis, Evolution and Reengineering (SANER), 2019

Go is a statically typed and compiled language, which has been widely used to develop robust and ... more Go is a statically typed and compiled language, which has been widely used to develop robust and popular projects. As other systems, these projects change over time. Developers commonly modify the source code to improve the quality or to implement new features. In this context, they use tools and approaches to support software maintenance tasks. However, there is a lack of tools to support Go developers in this process. To address these challenges, we introduce GoCity, a web-based implementation of the CodeCity program visualization metaphor for Go. The tool extracts source code metrics to create a software visualization in a automated way. We also report usage scenarios of GoCity involving three popular Go projects. Finally, we report the feedback of 12 developers about the GoCity of their projects.

Download

On the use of replacement messages in API deprecation: An empirical study

J. Syst. Softw., 2018

Libraries are commonly used to support code reuse and increase productivity. As any other system,... more Libraries are commonly used to support code reuse and increase productivity. As any other system, they evolve over time, and so do their APIs. Consequently, client applications should be updated to benefit from better APIs. To facilitate this task, API elements should always be deprecated with replacement messages. However, in practice, there are evidences that API elements are deprecated without these messages. In this paper, we study questions regarding the adoption of deprecation messages. Our goal is twofold: to measure the real usage of deprecation messages and to investigate whether a tool is needed to recommend them. We assess (i) the frequency of deprecated elements with replacement messages, (ii) the impact of software evolution on this frequency, and (iii) the characteristics of systems that deprecate API elements in a correct way. Our analysis on 622 Java and 229 C# systems shows that: (i) on the median, 66.7% and 77.8% of the API elements are deprecated with replacement ...

Download

Do Developers Deprecate APIs with Replacement Messages? A Large-Scale Analysis on Java Systems

2016 IEEE 23rd International Conference on Software Analysis, Evolution, and Reengineering (SANER), 2016

As any other software system, frameworks and libraries evolve over time, and so their APIs. Conse... more As any other software system, frameworks and libraries evolve over time, and so their APIs. Consequently, client systems should be updated to benefit from improved APIs. To facilitate this task and preserve backward compatibility, API elements should always be deprecated with clear replacement messages. However, in practice, there are evidences that API elements are usually deprecated without such messages. In this paper, we study a set of questions regarding the adoption of deprecation messages. Our goal is twofold: to measure the usage of deprecation messages and to investigate whether a tool is needed to recommend such messages. Thus, we verify (i) the frequency of deprecated elements with replacement messages, (ii) the impact of software evolution on such frequency, and (iii) the characteristics of systems which deprecate API elements in a correct way. Our large-scale analysis on 661 real-world Java systems shows that (i) 64% of the API elements are deprecated with replacement m...

Monorepos: A Multivocal Literature Review

ArXiv, 2018

Monorepos (Monolithic Repositories) are used by large companies, such as Google and Facebook, and... more Monorepos (Monolithic Repositories) are used by large companies, such as Google and Facebook, and by popular open-source projects, such as Babel and Ember. This study provides an overview on the definition and characteristics of monorepos as well as on their benefits and challenges. Thereupon, we conducted a multivocal literature review on mostly grey literature. Our findings are fourfold. First, monorepos are single repositories that contain multiple projects, related or unrelated, sharing the same dependencies. Second, centralization and standardization are some key characteristics. Third, the main benefits include simplified dependencies, coordination of cross-project changes, and easy refactoring. Fourth, code health, codebase complexity, and tooling investments for both development and execution are considered the main challenges.

Download

REST vs GraphQL: A Controlled Experiment

2020 IEEE International Conference on Software Architecture (ICSA), 2020

GraphQL is a novel query language for implementing service-based software architectures. The lang... more GraphQL is a novel query language for implementing service-based software architectures. The language is gaining momentum and it is now used by major software companies, such as Facebook and GitHub. However, we still lack empirical evidence on the real gains achieved by GraphQL, particularly in terms of the effort required to implement queries in this language. Therefore, in this paper we describe a controlled experiment with 22 students (10 undergraduate and 12 graduate), who were asked to implement eight queries for accessing a web service, using GraphQL and REST. Our results show that GraphQL requires less effort to implement remote service queries when compared to REST (9 vs 6 minutes, median times). These gains increase when REST queries include more complex endpoints, with several parameters. Interestingly, GraphQL outperforms REST even among more experienced participants (as is the case of graduate students) and among participants with previous experience in REST, but no prev...

Download

Migrating to GraphQL: A Practical Assessment

2019 IEEE 26th International Conference on Software Analysis, Evolution and Reengineering (SANER)

GraphQL is a novel query language proposed by Facebook to implement Web-based APIs. In this paper... more GraphQL is a novel query language proposed by Facebook to implement Web-based APIs. In this paper, we present a practical study on migrating API clients to this new technology. First, we conduct a grey literature review to gain an in-depth understanding on the benefits and key characteristics normally associated to GraphQL by practitioners. After that, we assess such benefits in practice, by migrating seven systems to use GraphQL, instead of standard REST-based APIs. As our key result, we show that GraphQL can reduce the size of the JSON documents returned by REST APIs in 94% (in number of fields) and in 99% (in number of bytes), both median results.

Download

REST vs GraphQL: A Controlled Experiment. (arXiv:2003.04761v1 [cs.SE])

arXiv Computer Science, Mar 11, 2020

GoCity: Code City for Go

2019 IEEE 26th International Conference on Software Analysis, Evolution and Reengineering (SANER), 2019

Download

On the use of replacement messages in API deprecation: An empirical study

J. Syst. Softw., 2018

Download

Do Developers Deprecate APIs with Replacement Messages? A Large-Scale Analysis on Java Systems

2016 IEEE 23rd International Conference on Software Analysis, Evolution, and Reengineering (SANER), 2016