Few other points to add: uWSGI has many advantages in a cluster infrastracture:
- a centralized memcached like k-v system with persistence - a scheduler/timer that could replace crontab and do more. - a complete set of signal system that allows you to do post-response background tasks. - you can offload tasks to other language that speaks uwsgi protocol. - a simple RPC system A timer/scheduler that could be programmed is a killer feature IMHO. Easy to deploy & manage time based tasks, and dynamic change them. btw Brubeck.io is a cool project, thanks! On Tue, Jan 29, 2013 at 12:30 PM, Xuanyi Chew <[email protected]> wrote: > Brubeck.io check it out. > > Xuanyi Chew > +61403928398 > > > > > On Tue, Jan 29, 2013 at 3:18 PM, est <[email protected]> wrote: > >> Hi all, >> >> Just some random thoughts about Mongrel2 >> >> To my understanding, Mongrel2 has many similarities with wsgi >> architecture and uWSGI container. >> >> - Mongrel2 speaks ZeroMQ, uWSGI speaks wsgi >> - Mongrel2 has N:M Messaging Pattern, uWSGI has something different >> called FastRouter to balance/multicast traffic to different clusters/workers >> - Mongrel2 is kinda like a container, uWSGI also supports python, RoR, >> php, Erlang, etc. >> >> But uWSGI has many interesting features like Zerg mode for auto scaling, >> Emperor mode, cluster, etc. uwsgi the messaging protocol is not only a >> wrapper for http but also a cluster control protocol. >> >> What do you guys think about uWSGI vs Mongrel2? Could these two inspire >> each other? >> > >
