Did you intend to close all open issues? about akkadotnet-code-samples

[Rainmaker52]

Yes. Thank you for the explanation. I'm excited to see some new samples in this repo. Thank you.

[M0ns1gn0r]

Without any answer. A strange act.

[Aaronontheweb]

I did and I meant to post this right after doing so #94

But unfortunately I was interrupted by several hours worth of meetings prior to finishing my thoughts there. We're basically overhauling this repository to modernize / streamline all of the samples since they've byte-rotted quite badly. I judged that the cost of updating these samples was too high given their age so I thought it best to begin with a clean slate.

Some of the more popular examples from this repository, such as WebCrawler, have been moved to their own repository. You can see a full list of some of the big "domain" examples here: https://getakka.net/articles/examples.html

But otherwise, I have a list of samples that we intend to add over the coming months (from an internal document I've been working on):

• Akka.Cluster Samples
  • Akka.Cluster w/ Multiple Role Types
    • Using a round-robin router
  • Akka.Cluster.Sharding + Akka.Persistence Storage using SQL Server
    • With remember-entities
    • With Google.Protobuf serialization
    • With ShardRegionProxy
  • Akka.Cluster.Singleton
    • Multiple role types
    • ClusterSingletonProxy
• Akka.Persistence Samples
  • Using SQL Server
    • Using Google.Protobuf Serialization
  • Using MongoDb
  • Using Redis
• Akka.Streams Examples
  • Akka.Streams.Kafka + Clustered ActorSystem
    • Each node reading from the same stream
    • Need to demonstrate safety around message handling (NO MISSED MESSSAGES, avoid duplicates)
  • RabbitMQ + Clustered ActorSystem
    • Each node reading from the same stream
      • Could have a singleton reader here to simplify this
    • Need to demonstrate safety around message handling (NO MISSED MESSSAGES, avoid duplicates)

These are all meant to be shovel-ready samples that will help Akka.NET users fall into the "Pit of Success," so to speak. If I've errored or destroyed what you feel is a valuable sample in the process, I am very interested in knowing that so I can act accordingly and bring it back. Does this help explain things?

[Aaronontheweb]

@M0ns1gn0r @Rainmaker52 did you see my previous comments?