Managing Complex Application State with Reactive Data Flows🔒 SSL Verified

Table of Contents

• ↓ Four building blocks
• ↓ Ebb at the edges
• ↓ Domino
• ↓ Reusable rules and views
• ↓ The UI layer
• ↓ The dashboard example
• ↓ Top Alternatives to yogthos.net

6-Month Traffic Trend Estimate

Visual representation extracted from yogthos.net

Content Snippets from yogthos.net

"(iterate   think   thoughts)"

"Reactive UIs look deceptively easy in a small app where you can keep things in sync without much effort. The trouble begins 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."

"The 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 gives us a clean way to coordinate data flows in and out of the system."

"All these pieces happen to fit together in a neat way. Ebb sits at the edges and coordinates external events coming into the system. Those events get transacted in Domino, where any derived values are calculated, and then a glimmer reactive atom drives the UI updates based on the resulting state. User input flows the other way going from the UI into Domino, getting transacted and triggering effects that flow back out of the system through Ebb."

Key Topics & Focus Areas for yogthos.net:

Four building blocks

Ebb at the edges

Domino

Reusable rules and views

The UI layer

The dashboard example