I propose that we can extend Mirrors to operations, and use the most natural DSL of all - plain trait definitions.

Can we derive endpoints from just a trait definition? One of Scala's strengths is domain modelling, and from a data definition, we can derive generic information in a Mirror, e.g. to generate type classes. For operations (such as endpoints) there is less support from metaprogramming, so we often create DSLs to describe them. I propose that we can extend Mirrors to operations, and use the most natural DSL of all - plain trait definitions.
This presentation describes the development of a financial middleware that internationally connects several ERP systems (Navision and SAP) to a cloud-based invoicing solution.
In this beginner-friendly talk we'll try to find out using the power of Scala and functional programming techniques.
We managed to alleviate almost entirely the slowdown induced by Tapir in a web socket server. The journey towards this goal was quite insightful, and we would like to share it with you.
I would like to go over the most relevant tools and changes that can improve your developer experience.
In this talk, we will take a tour around the `error` function. Starting from the simple use-cases and ending up with sophisticated yet developer-friendly error messages.
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.