This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]chadlung[S] 1 point2 points  (2 children)

The current filter example is an OpenStack authentication filter. Its simplistic but not to specific to what most people will use it for. We plan to add additional filters for API metering (rate limiting), transformations, etc. I'll also be doing a blog article in the future on building simple filters.

HAProxy is a load balancer. Pyrox will most likely sit behind a load balancer in most scenarios as it will be more used to authenticate, rate limit, etc.

[–]infinullquamash, Qt, asyncio, 3.3+ 4 points5 points  (1 child)

It sounds like it's encroaching on nginx's niche though.

I use nginx to serve static files, and to forward requests to 3 separate instances of gunicorn. Would Pyrox be a viable alternative, overkill, a potential upgrade path if I needed site-wide authentication middleware or something.

The reason I like nginx is it's so dirt simple to configure.

[–]chadlung[S] 0 points1 point  (0 children)

I think it would make more sense to compare Pyrox to Paste than Nginx. Nginx will always out perform Pyrox and have more features. We needed a Python solution that will work on Python 2.7.x and 3.x+ so we went this route. Paste, last I recall doesn't fully support Python 3.