Pith. Sign in

RECORD

Infrastructure in Code: Towards Developer-Friendly Cloud Applications

PaperPDF from arXiv

data files

Paper breakdownThe authors' claims, conditions and measurements, as JSON Signed receiptProof this review has not been altered
X Bluesky LinkedIn Reddit Hacker News
Vladislav Tankov, Dmitriy Valchuk, Yaroslav Golubev, Timofey Bryksin

Software Engineering · Submitted 17 Aug 2021

abstract compiled · 2026-09-23 · no language-model review

The authors' main claim Finally, we showcase the usefulness of Kotless by demonstrating its efficiency in migrating an existing application to a serverless environment.

how it is stated · asserted 1.00 read the record →

Comment (0) Read on arXiv ↗
Cite ▾
arXiv ID2108.07842 (version 1)
Pith IDE2FME4N6, Pith's permanent record of this paper and its review
CitationDmitriy Valchuk, Timofey Bryksin, Vladislav Tankov, Yaroslav Golubev. "Infrastructure in Code: Towards Developer-Friendly Cloud Applications." arXiv:2108.07842 (2021). https://pith.science/paper/E2FME4N6
Claim paper

The compiled record

The paper's own sentences, arranged. Each label is drawn from a closed vocabulary; the number beside it is the probability the classifier gave that label. Numbers in the tables are the authors', checked by code. No sentence in this record was written by a model.

Open the compiled record

Compiled by classifier-1.13.0 via TypeSafe API, question bank abstract-p1-20260923, 2026-09-23: 1 request, 4,324 input tokens.

What the abstract itself states, as probabilities: claims first 0.08 · states limitation 0.13 · human participants 0.04 · controlled comparison 0.06 · randomized assignment 0.01 · states quantitative result 0.65 · compares with prior results 0.66 · mentions code or data availability 0.07.

The abstract, sentence by sentence

arXiv listing abstract v1. Results and the main claim are underlined; .

The popularity of cloud technologies has led to the development of a new type of applications that specifically target cloud environments. Such applications require a lot of cloud infrastructure to run, which brought about the Infrastructure as Code approach, where the infrastructure is also coded using a separate language in parallel to the main application. In this paper, we propose a new concept of Infrastructure in Code, where the infrastructure is deduced from the application code itself, without the need for separate specifications. We describe this concept, discuss existing solutions that can be classified as Infrastructure in Code and their limitations, and then present our own framework called Kotless - an extendable cloud-agnostic serverless framework for Kotlin that supports two cloud providers, three DSLs, and two runtimes. Finally, we showcase the usefulness of Kotless by demonstrating its efficiency in migrating an existing application to a serverless environment.

background contribution method result interpretation main claim

What the classifier reports for each sentence. The number is the probability it gave the label.
#sentencerolethe authors' own workstates the main conclusionstrength
s0 The popularity of cloud technologies has led to the development of a new type of applications that specifically target cloud environments. background 1.00 0.04 0.02 asserted 1.00
s1 Such applications require a lot of cloud infrastructure to run, which brought about the Infrastructure as Code approach, where the infrastructure is also coded using a separate language in parallel to the main application. background 1.00 0.04 0.03 asserted 1.00
s2 In this paper, we propose a new concept of Infrastructure in Code, where the infrastructure is deduced from the application code itself, without the need for separate specifications. contribution 1.00 0.57 0.41 asserted 0.98
s3 We describe this concept, discuss existing solutions that can be classified as Infrastructure in Code and their limitations, and then present our own framework called Kotless - an extendable cloud-agnostic serverless framework for Kotlin that supports two cloud providers, three DSLs, and two runtimes. contribution 0.99 0.90 0.18 asserted 0.98
s4 Finally, we showcase the usefulness of Kotless by demonstrating its efficiency in migrating an existing application to a serverless environment. result 0.51 0.92 0.29 asserted 1.00

What kind of paper the classifier reports this is: method or tool 1.00 · evidence from observation or experiment 0.62.

What was examined, and what was not

sources read
  • arXiv listing abstract v1
not examined
  • full text
  • figures and tables
  • references and citing sentences
  • relations to other papers
levels run
  • P abstract
not run
  • S sections
  • T body sentences
  • C citations
  • R cross-paper relations

Every quoted sentence on this record is the authors'. Every label is from Pith's closed vocabulary, with the probability shown beside it. Every number in the measurements table is the authors', checked by code. Record as JSON

The paper
Original abstract

The popularity of cloud technologies has led to the development of a new type of applications that specifically target cloud environments. Such applications require a lot of cloud infrastructure to run, which brought about the Infrastructure as Code approach, where the infrastructure is also coded using a separate language in parallel to the main application. In this paper, we propose a new concept of Infrastructure in Code, where the infrastructure is deduced from the application code itself, without the need for separate specifications. We describe this concept, discuss existing solutions that can be classified as Infrastructure in Code and their limitations, and then present our own framework called Kotless - an extendable cloud-agnostic serverless framework for Kotlin that supports two cloud providers, three DSLs, and two runtimes. Finally, we showcase the usefulness of Kotless by demonstrating its efficiency in migrating an existing application to a serverless environment.

Human review

How Pith checks papers → · Full audit of this paper →

How the literature uses it

2 arXiv papers cite this in 4 sentences

Each citing sentence is taken from the citing paper's LaTeX source and typed by Pith's classifier. A label appears at probability 0.8 or more (0.95 for support), a contest at 0.7 or more; the quoted words are the citing authors'. How each label was checked · JSON

Papers citing it · 3 sentences without a confident label

Uses its method or tool 1 paper

What it cites · 2 sentences without a confident label

Cites as support 1 paper
  • As noted by Baldini et al. [ref] , the inability to automatically convert existing applications into cloud-native (serverless, in this case) is one of the biggest challenges for cloud adoption as a whole.

    Serverless Computing: Current Trends and Open Problems · Development API · 0.99

Discussion

Know something about this paper? Leave a comment, or highlight any passage above to comment on it.