LOADING
In this talk, I'd like to share how the Iron library and features from Scala 3 helped us build a solution which is safer, more robust, and easier to maintain.
This just crept up on us. Being a team responsible for integrations with external communication providers (smses, emails, etc), one day we woke up realising that a lot of of our work is managing changes to templates - handling other teams' requests to add or alter them, testing, making sure the timing is correct, storing in different data stores, and making sure they work correctly with different external providers. This took time and effort, and it was easy to make a mistake, causing incidents in production. We decided it's time to automate it. In this talk, I'd like to share how the Iron library and features from Scala 3 helped us build a solution which is safer, more robust, and easier to maintain.
In this presentation you will learn the source of your issues, and a third way - sanely-automatic derivation which is fast to compile, fast to run, and easy to debug by its users.
During the talk, we’ll build a small effect system using solely Scala 3 context functions step-by-step.
In this talk, I'll walk you through how workflows4s works, how it stands apart from tools like Temporal or Camunda, and why it just might be the better approach for modern, event-driven applications.
I will demonstrate how Pillars can take you from zero to production in record time. By leveraging Pillars’ integration of well-known libraries, you can bypass the usual complexities of setting up observability (traces, metrics, and logs), database access, API calls, and feature flag management.
In our talk, we will introduce a novel approach to system design— TypeOps — in which the application and infrastructure layers are fused to provide unprecedented safety and productivity for Scala teams.
In this talk, I will discuss why it's hard to use the power of RT to test side-effect-heavy apps.
