real-time-fes-kalix-laminar-example reviews and mentions

• Real-time frontends with Kalix and Laminar
  1 project | dev.to | 26 Nov 2022

  To really keep everything in sync it is important to replay the events in the same way on every sides. For that purpose, we share between backend and frontends the same definition of events and the same scala code for the replay. This sharing not only help for having things in sync but also to avoid redefining the same thing again at frontend. Very often, we define data model in the backend and then the same in the different frontends. Here we would like to avoid that and define it once in Kalix and reuse it in the Laminar frontends (web, mobile). Reusing the exact same scala code for the replay is really important. It saves you from out of sync problems. If you have different code (probably also different languages) for the replay between backend and frontend, you start quickly to have big problems, bugs and data problems. Think of a mobile app you need to redeploy to fix those problems (Mobile deployment is not straightforward). To illustrate my point, I have created a small example. The domain is crowd funding. The replay logic is very simple and minimal but it's just an example. Code can be found here: https://github.com/domschoen/real-time-fes-kalix-laminar-example The repository contains 3 projects: