4 ms·
I wrote this article a couple of months ago and didn't expect it to appear on my news feed all of the sudden. Thanks for the love everyone. Any questions are we
by pul 7y ago
I wrote this article a couple of months ago and didn't expect it to appear on my news feed all of the sudden. Thanks for the love everyone. Any questions are welcome of course!
- Baeocystin 7y agoHow do you like the .17 update? :D More seriously, I am curious about what people who haven't played Factorio think of the article. Since I've sunk $bignum hours in to it, I found your explanations clear, but I'd like to hear what those who haven't think.
- IggleSniggle 7y agoI haven’t played Factorio, and have just barely used Kafka. Therefore, if there was any subtlety, it was lost on me. Nonetheless, this article was clear. I thought this cute and I liked it, but I’m not sure that I gained any new insights into Kafka. This is not a criticism! However, one of the main advantages of Kafka, I thought, was that it’s so much more than a queue, since data is replayable, etc. The article does mention this as a shortcoming of the analogy, but isn’t this one of the main selling points vs other message queues?
- jand 7y agoI really enjoyed reading this, thank you very much. Please check the picture with the label "All microservice instances consume all messages". From my understanding it is more of a depiction of a consumer group. As factorio really consumes the messages (they are gone once consumed) you cannot really implement "All microservice instances consume all messages". Maybe this is BS, i have no Kafka expertise.
- pul 7y agoYou're absolutely right. There's no correct way to visualize this in Factorio.