Owin vs Waitress

Overview

Waitress

Stacks16

Followers58

Votes7

GitHub Stars1.5K

Forks182

Owin

Stacks867

Followers20

Votes0

GitHub Stars156

Forks47

Waitress vs Owin: What are the differences?

Developers describe Waitress as "*A production-quality pure-Python WSGI server *". It is meant to be a production-quality pure-Python WSGI server with very acceptable performance. It has no dependencies except ones which live in the Python standard library. It runs on CPython on Unix and Windows under Python 2.7+ and Python 3.4+. It is also known to run on PyPy 1.6.0 on UNIX. On the other hand, Owin is detailed as "A standard interface between .NET web servers and web applications". It is a standard for an interface between .NET Web applications and Web servers. It is a community-owned open-source project.

Waitress and Owin can be categorized as "Web Server Interface" tools.

Waitress and Owin are both open source tools. Waitress with 640 GitHub stars and 94 forks on GitHub appears to be more popular than Owin with 149 GitHub stars and 51 GitHub forks.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Detailed Comparison

Waitress	Owin
It is meant to be a production-quality pure-Python WSGI server with very acceptable performance. It has no dependencies except ones which live in the Python standard library. It runs on CPython on Unix and Windows under Python 2.7+ and Python 3.4+. It is also known to run on PyPy 1.6.0 on UNIX.	It is a standard for an interface between .NET Web applications and Web servers. It is a community-owned open-source project.
Production-quality WSGI server ; Dont hang a thread up trying to send data to slow clients;Use self.logger to log socket errors instead of self.log_info (normalize); Remove pointless handle_error method from channel; Queue requests instead of tasks in a channel	-
Statistics
GitHub Stars 1.5K	GitHub Stars 156
GitHub Forks 182	GitHub Forks 47
Stacks 16	Stacks 867
Followers 58	Followers 20
Votes 7	Votes 0
Pros & Cons
Pros 2 Runs on Windows 1 Easy setup 1 Reliable 1 Light 1 Fast	No community feedback yet
Integrations
Windows Python Flask	.NET .NET Core ASP.NET

What are some alternatives to Waitress, Owin?

uWSGI

The uWSGI project aims at developing a full stack for building hosting services.

Xen Orchestra

It provides a web based UI for the management of XenServer installations without requiring any agent or extra software on your hosts nor VMs.

Werbot

It is basically a platform for storing, sharing, and managing server access. But the most valuable part of it concerns the possibility to do an audit and to control the work performed on the server. Our platform can be integrated as an independent service in company infrastructure. It doesn’t change the way developers are used to working on the server, it changes the way they connect on it. All connections to servers are made through a single sign-on and private user access. All the actions performed on servers and in Werbot web interface are logged and recorded (screencasts). The server administrator can not only see what was done on the server by each user and when it was done but also can replay the whole working session in our player. The server audit is made much easier with Werbot.

Related Comparisons

Waitress and Owin are both open source tools. Waitress with 640 GitHub stars and 94 forks on GitHub appears to be more popular than Owin with 149 GitHub stars and 51 GitHub forks.

Owin vs Waitress