This probably isn't an immediate need but is worth thinking about from an architectural standpoint. We will want to migrate to an interactions endpoint url via web requests as opposed to the gateway so that we can load balance and build bits into a k8 cluster for scaling. This doesn't matter until we're at like 10k users probably, but at that point it allows us to handle massive load variance really elegantly and if we develop this way now it ensures we don't end up in sticky spots as we try to transition it. Challenges like "the worker will need to scale independent of the database and configuration" etc
This probably isn't an immediate need but is worth thinking about from an architectural standpoint. We will want to migrate to an interactions endpoint url via web requests as opposed to the gateway so that we can load balance and build bits into a k8 cluster for scaling. This doesn't matter until we're at like 10k users probably, but at that point it allows us to handle massive load variance really elegantly and if we develop this way now it ensures we don't end up in sticky spots as we try to transition it. Challenges like "the worker will need to scale independent of the database and configuration" etc