As we're working on building out our content platform we added the ability to subscribe to collections a couple weeks ago so people could get email notifications when you publish a new article. All started great until we onboarded a befriended german non-profit with almost 700 subscribers and I realized not all subscribers got their mail and the servers would kinda randomly crash. The 2+ webhook events we receive for each email sent, would each read & write multiple times to the database, while still in the process of sending out more emails. From my current understanding this got the current system overwhelmed. I was confident the current architecture would handle this still small load, as I was already using a message queue to slow down sending, so it would spread the load. We're currently in the process of improving the whole queuing system, but especially utilizing a message queue for incoming webhooks and edge workers for processing of that queue to ease the load of our servers. In the meantime feel free to test the feature and report any bugs you encounter along the way! Trying to share more going forward, especially upcoming features we've got in the works, as we're especially excited about the planned editing experience 🤗 Can PS: Feel free to leave a comment here with thoughts, ideas etc 😇
