Essays about: "API Versioning"

Found 5 essays containing the words API Versioning.

1. 1. Proactive Mitigation of Deprecated API Version Usage : Utilizing continuous integration to automatically and proactively detect deprecated API version usage in microservice ecosystems

   University essay from Uppsala universitet/Institutionen för informatik och media

   Author : Eric Nilsson; [2021]
   Keywords : Microservices; Continuous Integration; Proactivity; Automaticity; API; API Versioning; Deprecation; Data Integration; Ontology Matching; Design Science Research;

   Abstract : The notion of change is one of the more pronounced challenges API developers face, since a change to published APIs means a change for its’ consumers. API Versioning is a commonly used strategy to mitigate the risks of changing APIs, however, the strategy introduces a possibility of having practically innumerable number of API versions published at once, all possibly used by different consumers, creating considerable overhead for API developers to manage. READ MORE

3. 2. GitHub Visualizations and their Usefulness for GitHub Users

   University essay from KTH/Skolan för elektroteknik och datavetenskap (EECS)

   Author : Daniel Sahlin; Christian Stjernberg; [2020]
   Keywords : ;

   Abstract : The most popular versioning system is undoubtedly Git, for which GitHub with its 40 million users provides a central location at which Git repositories can be discovered and contributed to. With all of the metadata that Git repositories contain, GitHub also holds a significant amount of data in its 44 million repositories which can be accessed freely with the GitHub API. READ MORE

4. 3. Plutt: A tool for creating type-safe and version-safe microfrontends

   University essay from KTH/Skolan för elektroteknik och datavetenskap (EECS)

   Author : Julius Recep Colliander Celik; [2020]
   Keywords : Plutt; Microfrontends; Microservices; Semantic Versioning; Lock-step deployments; Type safety; Access transparency; Plutt; Mikrofrontends; Mikrotjänster; Semantisk Versionering; Lock-step deployments; Typsäkerhet; Access transparency;

   Abstract : Microfrontend applications are composed of multiple smaller frontend applications, which are integrated at run-time. As with microservices, microfrontends can be updated in production at any time. There are no technological restrictions for releasing API-breaking updates. READ MORE

5. 4. An empirical investigation into problems caused by breaking changes in API evolution

   University essay from KTH/Skolan för elektroteknik och datavetenskap (EECS)

   Author : Erik Dackebro; [2019]
   Keywords : ;

   Abstract : To evolve an API, providers update the API and publish new versions, which consumers have to adopt. As the API defines the interface to a service, changing it can have severe consequences to consumers. To ease the transition between versions, semantic versioning was introduced and despite its good intention, many problems still remain. READ MORE

6. 5. Geo-Replicated Buckets : An Optrimistic Geo-Replicated Shim for Key-Value Store

   University essay from KTH/Skolan för informations- och kommunikationsteknik (ICT)

   Author : João Neto; [2015]
   Keywords : ;

   Abstract : This work introduces GeoD and VersionD. GeoD is a causally-consistent georeplication shim for key-value stores. GeoD enables the separation of concerns regarding replication and convergence from key-value stores, while preserving all of their read-only functionality. READ MORE