Managing Complex Application State with Reactive Data Flows 0 ▲ (iterate think thoughts) 1 hour ago · 10 min read2002 words · Tech · hide · 0 comments Reactive UIs look deceptively easy in a small app where you can keep things in sync without much effort. The trouble starts once the app starts to grow and accumulate real business logic. You often end up with cascading sets of rules that depend on derived values. On top of that, some of the data has to flow out to external services while more keeps coming in from them back into your application. Ensuring that all of it stays consistent while the user is busy clicking things and entering data in the UI is not trivial, as anybody who's built these kinds of apps knows.Four building blocksThe good news is that we can use four building blocks to break the problem down. Datastar and glimmer give us an easy way to create a reactive UI that responds to changes in the data. Domino provides a transactional data flow engine which encodes all the business logic. Ebb, which is a port of Missionary to Jolt, gives us a clean way to coordinate data flows in and out of the system.All these pieces… No comments yet. Log in to reply on the Fediverse. Comments will appear here.