Connecting...

W1siziisimnvbxbpbgvkx3rozw1lx2fzc2v0cy9zawduawz5lxrly2hub2xvz3kvanbnl2jhbm5lci1kzwzhdwx0lmpwzyjdxq

Descriptions, APIs and Tapirs by Adam Warski

W1siziisijiwmtkvmduvmtqvmtyvmjgvmtcvmti1l0lnr18znjkwlmpwzyjdlfsiccisinrodw1iiiwiotawedkwmfx1mdazzsjdxq

Did you catch Adam Warski's talk at Scala in the City?

The CTO of SoftwareMill came to London to give an exclusive talk for our attendees! Adam helped us get through coding challenges by demonstrating how Tapir impacts the "approachability" aspect of the API.

 

Descriptions, APIs and Tapirs

It might seem that defining HTTP APIs in Scala is a solved problem. Or is it? Tasks such as generating Swagger documentation or auto-generating clients have always been a challenge. 
 
Let's fix this! We'll apply an approach of separating the **description** of a problem from its **interpretation**. This has proven to be a powerful tool in other domains (e.g. modeling side effects or database access), so let's see how it works for HTTP APIs. 
 
In this **live-coding** talk we'll go through the main features of [Tapir](https://github.com/softwaremill/tapir), discuss some of the design decisions and challenges, demonstrate the type-safety and how it impacts the "approachability" aspect of the API.