Scott Clasen

@pkrull seems reasonable, fancy trying your hand at a PR?

:) Maybe just make it func Handers() map[string]*ActivityHandler and return a copy of the handlers map?

Sounds fine, as long as the log levels dont necessarily appear in all the log lines. We would also need to have some guidelines for determining what is debug/info/error etc.

not really docs, but the tests have 3 examples of coordinated handlers here https://github.com/sclasen/swfsm/blob/master/activity/coordinated_worker_test.go#L177-L254 the tick counting example maintains state, which is used in the test here https://github.com/sclasen/swfsm/blob/master/activity/coordinated_worker_test.go#L172

@ryanwalls yeah, so lets take the example of running some sort of long running job. Start would start the job running. Tick would monitor the job, perhaps returning updates if...

Of course you could do slightly different things with Start and Tick too. Start could verify that you could connect to a queue or some such, and Tick could poll...

hey @nefilim I would definitely suggest performing benchmarking and tuning required throughput for your specific workload. You can get cloudwatch metrics that will tell you about what throttling is happening...

One knob you can turn to speed recovery is the `sequence-shards` property which defaults to 1000, which takes 10 requests to read all shards for a Persistent actor. If reduced...

Aha, got it. yes it does seem to be the naiive approach. Saw your post on akka-user too. the seq is per actor (it was global in eventsourced, but is...

Hitting this behavior ATM, was there any decision on what to do here?