Minimum judge about bugout HOT 10 CLOSED

Inspiration: https://docs.confluent.io/current/tutorials/examples/microservices-orders/docs/index.html#tutorial-microservices-orders

from bugout.

An example which uses lists in aggregates:

https://ericlondon.com/2018/07/26/kafka-streams-java-application-to-aggregate-messages-using-a-session-window.html

from bugout.

Another relevant example which has a "top 3" data structure

https://technology.amis.nl/2017/02/12/apache-kafka-streams-running-top-n-grouped-by-dimension-from-and-to-kafka-topic/

from bugout.

Advanced by #11

from bugout.

You'll want to make sure you can reconstruct the game'shl history of moves using the game state table entry, since replaying using Kafka itself is inefficient (see #6)

from bugout.

Since we only need move history at the end of a game, store pieces in a map of Coord->Player

Track the current turn number

Track whose turn it is

Keep an ordered list of (Player,Turn) so that we know when players passed

Represent passing explicitly in move event (null or some named type)

from bugout.

https://github.com/confluentinc/kafka-streams-examples/blob/master/src/test/scala/io/confluent/examples/streams/StreamToTableJoinScalaIntegrationTest.scala

https://docs.confluent.io/current/streams/concepts.html#globalktable

from bugout.

https://www.confluent.io/blog/distributed-real-time-joins-and-aggregations-on-user-activity-events-using-kafka-streams/

from bugout.

Cycles https://www.instaclustr.com/kongo-5-3-apache-kafka-streams-examples/

from bugout.

https://stackoverflow.com/questions/44275301/kafka-stream-and-kafka-table-one-to-many-relationship-join

from bugout.