|
|
|
|
|
by eatonphil
1392 days ago
|
|
This is a fine article but I find the jump from > This works reasonably well. The polling period of reading the events may become a problem, but you can make it better by using database triggers. to > But when we look at tailored backends in the open, especially in architectures for FAANG, MAMAA, or whatever the acronym is until the next time Zuck decides to pivot Facebook, things look different. unsatisfying. Somewhere I'd love the walkthrough of in what scenarios exactly does the database-as-event-store+ad-hoc-worker architecture fall over rather than immediately jumping to what "the pros" do. That's more of an appeal to authority rather than something I can learn from. Not saying you need to do this in your article but if not at least a link to read more would be welcome. :) |
|
I thought of that myself to be honest but the article was becoming too long and decided to cap. Great point about the link, that's great feedback!