LOADING
Avoid mistakes in API design, implementation and evolution with Smithy
Most back-end projects eventually reach a point when they have to define an API. We implement their routes, document them, sometimes we write a client. We do essentially the same work multiple times - each view of an endpoint contains the same path, and yet we don't have a "single source of truth".
In this talk, I'll show how Smithy (https://smithy.io) and smithy4s enable defining an API in a single place, and how they make it easy to build its server, client, and even a CLI - in a Scala-friendly, tooling-compatible way.
Let's take a look at the issues that enums have in Scala 2 and whether we found the Holy Grail with the introduction of Scala 3.
As WebAssembly matures and gets more and more traction from the community, you might wonder can Scala join that trend?
We all have pretty little things laying around in our codebases, yet, we seldom give them the same love
Learn about opaque types and add this new tool to your modelling toolbox!
