You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This discussion on Hacker News got me thinking about the current necessity for the Lightbus worker to be run in its own process. Now Lightbus' threading has been sorted out, could we have the option of just running a Lightbus worker within the web process?
Why would anyone want to do this?
Pro: Simple sites become a single process (simpler deployment, less memory use)
Pro: Easier development workflow
Pro: Can use Lightbus where the number of processes is limited (i.e. Using Heroku's free dyno)
Why would this be a bad idea?
Con: High volume worker loads would impact serving of web requests
Con: Could increase Lightbus complexity
Con: More things to learn
Option 1 doesn't concern me, this is a fair trade-off which can be clearly explained. Option 2 concerns me more, and I would hope to mitigate this be (hopefully) avoiding having to modify the Lightbus core code. Option 3 is more concerning, I want to keep Lightbus simple and obvious, and this would be a wrinkle in the early tutorials.
How could this look?
Example WSGI for small site (using white noise for serving assets):
If this is going to ease development as well as deployment, then it needs to plug into development servers and not just ASGI/WSGI, which could be a whole other framework-specific problem.
Want this?
If you want this leave a comment or give the issue a 👍 reaction
The text was updated successfully, but these errors were encountered:
This discussion on Hacker News got me thinking about the current necessity for the Lightbus worker to be run in its own process. Now Lightbus' threading has been sorted out, could we have the option of just running a Lightbus worker within the web process?
Why would anyone want to do this?
Why would this be a bad idea?
Option 1 doesn't concern me, this is a fair trade-off which can be clearly explained. Option 2 concerns me more, and I would hope to mitigate this be (hopefully) avoiding having to modify the Lightbus core code. Option 3 is more concerning, I want to keep Lightbus simple and obvious, and this would be a wrinkle in the early tutorials.
How could this look?
Example WSGI for small site (using white noise for serving assets):
Adding in a lightbus worker could look something like this:
Thoughts
Want this?
If you want this leave a comment or give the issue a 👍 reaction
The text was updated successfully, but these errors were encountered: