This shows how the server-driven UI reacts to both immediate events and eventually-consistent changes, such as Slack updates in the background. There's no distinction between "controllers" and "background jobs". the UI reacts to events as they happen. #ruby #eventsourcing

RT @anders_murphy: The nice thing with #datastar being server driven is you can test the client by driving the server. Here, I'm testing g…

@MorriceGavin @lucianghinda Me trying not to take the bait

@seuross Event sourcing is just a pattern. Whether it scales or not depends on the implementation. Mine works similar to ActiveJob DB adapters, so it scales in the same way. What did you use?

@seuross What? What works in a single machine? Ruby?

Also exploring realtime UI patterns with Datastar

@TheDumbTechGuy 😮

@TheDumbTechGuy A nice use of this is, you can have a web component with props set as signals. Then the server can drive tue web component by sending signal updates to the client

@TheDumbTechGuy ... So it's good for regular req/resp updates, but also long-running background processes, real-time, eventually-consistent backends, etc etc.