Not sure how this server would operate with high frequency of updates, large resource sizes, and large numbers of subscribers. Items to consider:
Time, memory and CPU load required to send out every SubscriptionUpdate Oban job if there are 10s of thousands of subscribers on a large resource.
Size of database. WebSub adds the full resource content in each Update record in the database. These records should be purged within a few hours (?) of the last SubscriptionUpdate sent out. Develop a cron system to purge old records, or older Update records for the same resource could be deflated by setting their body value to an empty string.
Not sure how this server would operate with high frequency of updates, large resource sizes, and large numbers of subscribers. Items to consider:
SubscriptionUpdateOban job if there are 10s of thousands of subscribers on a large resource.Updaterecord in the database. These records should be purged within a few hours (?) of the lastSubscriptionUpdatesent out. Develop a cron system to purge old records, or olderUpdaterecords for the same resource could be deflated by setting theirbodyvalue to an empty string.