Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • 1
    Having worked in a system which used a message broker for database replication, I'd warn about first considering KISS, YAGNI and DRY, because you could very well end up with a system which violates all three of these. In this particular case, the database replication ended up being much larger and more complex than the rest of the system combined; it had dozens of extra microservices and infrastructure to provide sufficient resilience, reliability, recovery and observability, which caused a massive amount of pain diagnosing and fixing live environment issues. Commented Nov 8, 2020 at 12:19
  • @BenCottrell Hmm, yeah, that sounds like a burden. Thought, I prefer replication over aggregation services. Commented Nov 8, 2020 at 20:38