LOADING
In this talk, we’ll show first the different techniques we can use to apply constraints is our domains. Then, we’ll present Iron, its features, extensions, and integrations. We’ll finish by showcasing a fully integrated constraint-enforcing app.
When designing an application, we often end up with domain-specific types, that all behold constraints that we try to enforce as much as possible: an age is positive, a delivery date can’t be in the past, etc. Modelling the data right is a part of the success of Scala and functional programming in general, but it also brings either boilerplate (we have to do again and again validation), or rely purely on conventions.
But there is hope. Meet the Iron library.
Iron is, a type constraint library that allows us to have a safe, declarative and smarter model. It enables us to have a continuous stream of valid data from our API endpoints to the database, and removed a whole class of bugs. Using advanced features like opaque types, inlines and the new macro system, it offers a true 0 cost, 0 dependency library that doesn't hamper compile time.
In this talk, we’ll show first the different techniques we can use to apply constraints is our domains. Then, we’ll present Iron, its features, extensions, and integrations. We’ll finish by showcasing a fully integrated constraint-enforcing app.
Join me in a talk empowering you to build Scala applications that not only excel internally but also deliver optimal experiences from an external perspective.
In this talk, we will start with the basics, understanding what build caching is and why it can be a bit tricky to handle in real projects.
Let's write a game in Scala Native, for Playdate!
I propose that we can extend Mirrors to operations, and use the most natural DSL of all - plain trait definitions.
