Goal 4 - The server maintains and returns a shared store of state (Redux).

[deanrad]

Prev | Next

In this goal, we'll address the issue of persistence. We notice its lack when we have late-joining clients. And we'll lay the foundations for persistence to a database. These will be server-only changes.

First we'll see that:

• If a client joins after several others have sent holdRoom messages - the new client will not see the same rooms held as the others!

Then we'll make the following changes:

• Create a Redux store in the server's memory
• Respond to REST API calls with what's currently in the store
• Filter incoming holdRoom actions through the store

We'll verify that:

• Everything works, plus late-joining clients are in sync!

We've pretty much completed the app for demo purposes, and could call it done.
But, for one additional thing:

We now notice that:

• Room 20 simulated occupancy changes are not reflected in late-joining clients

And so we'll:

• Subscribe to simulated occupancy changes as well.

Then we'll really wonder if we want to use Redux in-memory or use a database. But we'll get the chance to add a database in the next Goal!

Prev | Next