UI in the sample makes it more complicated about akka-edge-rs HOT 8 CLOSED

One thing I’ve strived for with the example is to make it real. It bothers me that examples out there leave so much out. And I think the UI visually demonstrates something quite distinct about Akka’s event driven approach.

However, I get the burden it’s introducing on the first time reader. I can remove it from the guide and leave it in the example. Does that work for you both?

from akka-edge-rs.

Sounds good to me

from akka-edge-rs.

I think it would be fine to keep in the guide, as long as it was a separate step where you didn't have to understand it to get the core APIs.

Hiding it is also ok, but I think it still changes how things are done, for example, if you didn't do an SSE UI, would you have the shared model at all?

from akka-edge-rs.

if you didn't do an SSE UI, would you have the shared model at all?

Good question. When we get to the gRPC-web stuff I suspect that protobuf will become that shared model.

from akka-edge-rs.

Are we ok to close this now given https://github.com/lightbend/akka-projection-temp/pull/23. Life is now much simpler... WDYT?

from akka-edge-rs.

I think it is ok now that the concerns are better separated 👍

from akka-edge-rs.

Great improvement. Maybe the shared model separation is not that important any more? Anyway, we can fine tune later.

from akka-edge-rs.

I think there is still merit in the shared model. The UI is event sourcing its state to present to the user with the same methods that the backend is. This is also consistent with my production app, and I’ve found it to be very useful there.

from akka-edge-rs.