DEV Community


Kotlin DSL: An Introduction

Tim Britton
・3 min read

I am a pretty big proponent of Kotlin as a language and for the last three years, I have had the opportunity to build a platform utilizing Kotlin in conjunction with Vertx. I think one of the best parts of Kotlin is you can always discover a better way of doing something. In this article, I am going to discuss how to write a Kotlin DSL and provide a simple example of a DSL I wrote recently for one of my toy projects.

Let start by discussing what a DSL is in the first place. DSL stands for Domain Specific Language which I would further define as modifying the syntax of Kotlin to adhere to a given concept in your broader system.

Kotlin enables you to build these DSLs via specific language features the three features I want to highlight are Lambda Syntax, Higher-Order Functions and Extension Functions.

Lambda Syntax

The syntax for Lambda Functions is different than other languages and has some built-in functionality that is unique.

val listOfLetters = listOf("A", "B", "C").map{

//yields list ["a", "b", "c"]


  • The Lambda is not a parameter to map but is after the map function name.
  • The input to the Lambda is automatically given a name it

Higher Order Functions

Kotlin has higher-order functions which means you are able to pass functions into other functions

fun main(){
 val b =  {
//prints `B`
fun a(fn: () -> Unit){

Extension Functions

Extension Functions allow you to expand other classes with new functionality without updating the class itself.

class Cat() {

fun Cat.meow() {

fun main(){
val kitten = Cat()

//prints `MEOW`

When you combine these three features you are able to customize Kotlin to fit the needs of what you are working on.

For one of my toy projects, I'm working on I wrote a DSL for creating tables for generating random value objects.

When utilizing this DSL you can write the following:

        simpleTable<ActionCost>("Common Action Cost Table") {
            entry { 2.0 to ActionCost.ONE }
            entry { 30.0 to ActionCost.TWO }
            entry { 20.0 to ActionCost.THREE }
            entry { 20.0 to ActionCost.FOUR }
            entry { 18.0 to ActionCost.FIVE }
            entry { 10.0 to ActionCost.SIX }

What this code does is create a named table that associates a percentage to a give ActionCost. You can then call random() to get a random value from the table where if you call it 100 times you will likely get ActionCost.ONE two percent of the time.

The class yielded by the simpleTable method is:

Note: I'm not working with doubles because rounding sucks. Also wouldn't recommend using this on anything productive.

The DSL for constructing this data structure looks like so:

The DSL is composed of two extension methods providing the easy to use and understandable structure and the final extension validates the data within the structure since we want the percentage to add to 100.

When I wrote this DSL I wanted to be able to visually identify potential bugs with the percentages I assigned to a given entity and be able to quickly make a change to what could be a pretty large set of entries.

Well with that I hope you were able to learn something about how DSLs work in Kotlin. Feel free to drop a comment below If you have questions or comments or if you are interested in seeing other DSLs I have written.

If there is enough interest I might do a live rewrite of the Vertx Web DSL and write up an article on how to write a DSL for an existing framework.

Discussion (0)