> If the follower goes down, when it comes back it can page through the history at its leisure. There is no queue, nor workers on each end trying to pass events along as a bucket brigade.
Sure, there is no queue. There is an append only log. Kafka is not a queue but an append only log.
I do not like the proposed solution. I do not like it because it assumes that I have to maintain the infrastructure to do all the distributed logging on my end. As in, most likely I have to maintain a Kafka cluster.
There’s also one thing glossed over in this article. What if your consumer went past certain messages but it mishandled them? You can go to the past either.
If your consumer needs ordered delivery, web hooks might not be the best solution, indeed. But it might cost you more because I need additional infra to provide you with that.
Sure, there is no queue. There is an append only log. Kafka is not a queue but an append only log.
I do not like the proposed solution. I do not like it because it assumes that I have to maintain the infrastructure to do all the distributed logging on my end. As in, most likely I have to maintain a Kafka cluster.
There’s also one thing glossed over in this article. What if your consumer went past certain messages but it mishandled them? You can go to the past either.
If your consumer needs ordered delivery, web hooks might not be the best solution, indeed. But it might cost you more because I need additional infra to provide you with that.