API Management Maturity of Low-Code Development Platforms

Overeem, Michiel; Jansen, Slinger; Mathijssen, Max

doi:10.1007/978-3-030-79186-5_25

Cited by 6 publications

(4 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…An important missing feature is safety guards against public APIs. Earlier research [183] showed the importance of API management for LCDPs. Safety checks on these published APIs support the citizen developer in these tasks.…”

Section: Discussionmentioning

confidence: 99%

“…Based on the evaluations we discuss the importance of API management capabilities for LCPs in the enabling of the development of software ecosystems. This chapter was originally published as a conference article [183], and the evaluation data was made publicly available [184].…”

Section: Chapter 5 -Api Management Maturity Of Ldcpsmentioning

confidence: 99%

“…These discussions have bent the inward look from AFAS Focus to LCDPs in general. The research and development of AFAS Focus has resulted in contributions such as a comparison of model execution [182], a framework for data migration [186], and a maturity model for API management that is applied to LCDPs [183]. The Impact Analysis for Low-Code Development Platforms framework presented in Section 7.3 is based on the acquired knowledge, research contributions, and experience accumulated throughout these years.…”

Section: Research Approachmentioning

confidence: 99%

See 2 more Smart Citations

Evolution of Low-Code Platforms

Overeem¹

Self Cite

View full text Add to dashboard Cite

Event sourced systems are increasing in popularity because they are reliable, flexible, and scalable. In this article, we point a microscope at a software architecture pattern that is rapidly gaining popularity in industry, but has not received as much attention from the scientific community. We do so through constructivist grounded theory, which proves a suitable qualitative method for extracting architectural knowledge from practitioners. Based on the discussion of 19 event sourced systems we explore the rationale for and the context of the event sourcing pattern. A description of the pattern itself and its relation to other patterns as discussed with practitioners is given. The description itself is grounded in the experience of 25 engineers, making it a reliable source for both new practitioners and scientists. We identify five challenges that practitioners experience: event system evolution, the steep learning curve, lack of available technology, rebuilding projections, and data privacy. For the first challenge of event system evolution, we uncover five tactics and solutions that support practitioners in their design choices when developing evolving event sourced systems: versioned events, weak schema, upcasting, in-place transformation, and copy-and-transform.

show abstract

Section: Discussionmentioning

confidence: 99%

Section: Chapter 5 -Api Management Maturity Of Ldcpsmentioning

confidence: 99%

Section: Research Approachmentioning

confidence: 99%

See 1 more Smart Citation

Evolution of Low-Code Platforms

Overeem¹

Self Cite

View full text Add to dashboard Cite

show abstract

“…The first stage is critical in this research because the development of the web service must be data retrieval or delivery of services to data collected in a database (Overeem et al 2021) . After identifying and collecting the data obtained, the next stage is continued by building a web service.…”

Section: Figure 1 Research Methodsmentioning

confidence: 99%

Improving REST API Performances Using Design Patterns: A Case in Healthcare Business Intelligence Systems

Proceedings of the International Conference on Industrial Engineering and Operations Management

View full text Add to dashboard Cite

Managing a lot of data using a well-designed health information system can prevent medical errors and support doctors and medical service providers in providing the proper diagnosis to patients. This condition is inseparable from advances in data exchange technology commonly used, namely REST and SOAP. The REST API is beneficial in exchanging medical record data faster in real-time. Problems then arise as time goes by, where transactions significantly increase, creating a longer access time. This study solves the problem by adding design pattern technology using a caching pattern. The data retrieval process on the web service is stored in the cache so that when retrieving data, there is no need to re-query the database and then update the cache on the web service and update daily using Cron. This research uses a case study of a healthcare business intelligence system with various data taken from 3 different systems that have been integrated. Tests were carried out in on-premise and cloud server environments with variations between 5,000 and 10,000 data and tested 50 times each. After using the catching pattern, the measurement results of on-premise web services show a reduction in response time of up to 87%. For further development, an additional service is needed to manage caches that are simultaneously entered into the server so that RAM usage occurs optimally and does not cause data access time delays.

show abstract

Democratizing Software Development: A Systematic Multivocal Literature Review and Research Agenda on Citizen Development

Binzer

Winkler

2022

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

API Management Maturity of Low-Code Development Platforms

Cited by 6 publications

References 13 publications

Evolution of Low-Code Platforms

Evolution of Low-Code Platforms

Improving REST API Performances Using Design Patterns: A Case in Healthcare Business Intelligence Systems

Democratizing Software Development: A Systematic Multivocal Literature Review and Research Agenda on Citizen Development

Contact Info

Product

Resources

About