Good article! Congrats! Just one suggestion, which is a matter of taste, I would not put the code in the middle of the article. It is more comfortable to read the article and then if someone is interested, can check the code. Keep it going!
I don't think that solution resolves the problem you raised above about missing message. You also could take error during process the log change event. So I don't think it's the good approach
Thanks! I honestly think it makes it sound too simple even, but at least people should be aware of this topic, and then meet the pitfalls if they want to pursue this way.
Good article! Congrats! Just one suggestion, which is a matter of taste, I would not put the code in the middle of the article. It is more comfortable to read the article and then if someone is interested, can check the code. Keep it going!
Great feedback, thanks. Totally makes sense
Another alternative: Postgres logical replication
I don't think that solution resolves the problem you raised above about missing message. You also could take error during process the log change event. So I don't think it's the good approach
It has its own pitfalls for sure, but generally WAL can be more flexible.
Very well written Alex. This is a difficult topic but this post makes it sound so simple 😅
Kudos.
Thanks! I honestly think it makes it sound too simple even, but at least people should be aware of this topic, and then meet the pitfalls if they want to pursue this way.