It's decently scalable. If you're running Oxite on one web server it should work just fine. You can run into some troubles having it run inside the web application. If the web app goes down, your service does too. What's cool though is that it will
come back up when your app does though and it's disconnected enough to pick up where it left off.

For web farms we'd recommend creating a scheduled task to run the background service directly (just build a command-line app that instantiates the services and executes them at the intervals you want [no need for the BackgroundServiceExecutor stuff]) on each
node (or just one node in the farm) so it's a separate process and can run independently of the web app. This is how we do it on
Channel 9.