Echo JS 0.11.0

<~>
nerdalytics 4 days ago. link parent 1 point ▲ ▼
Beacon is backend-focused state primitives—metrics, config, service state. Not trying to replace Redux/Apollo.
You're right that transport/sync is the missing piece. That's on the roadmap as Beacon-Transport, but nothing publishable yet.

The plan: WebSockets with value diffing (not action/patch history). Last-write-wins. The advantage: recovering state is a single read instead of replaying patches—faster failure recovery.


Current ecosystem status:

Beacon (1000.2.3): Core reactivity—complete for my backend needs
Beacon-Durable (next release): SQLite-backed persistence, resumability
Beacon-Rules (following): FSM foundation
Beacon-Transport (future): Client sync over WebSockets

Replies

tracker1 3 days ago. link 1 point ▲ ▼
That's cool... and I literally meant Redux as a state machine on the server, have considered doing this for shared state app, and then sending JSON diffs to the client via WS, then client events likewise bubble to server as a round trip.

This would be for a shared learning environment/simulation... though could probably work for a game where some level of lag is tolerable.  Such as a shared board or card game, etc.