forked from erlyaws/yaws
-
Notifications
You must be signed in to change notification settings - Fork 0
Home
capflam edited this page Sep 8, 2011
·
12 revisions
When we started to redesign the Yakaz website architecture we questioned our choice of Apache as HTTP server and we tested Yaws.
From the Yaws website:
Yaws is a HTTP high perfomance 1.1 webserver particularly well suited for dynamic-content web applications. Two separate modes of operations are supported:
- Standalone mode where Yaws runs as a regular webserver daemon. This is the default mode.
- Embedded mode where Yaws runs as an embedded webserver in another Erlang application.
Yaws is entirely written in Erlang, and furthermore it is a multithreaded webserver where one Erlang lightweight process is used to handle each client.
The main advantages of Yaws compared to other Web technologies are performance and elegance. The performance comes from the underlying Erlang system and its ability to handle concurrent processes in an efficient way. Its elegance comes from Erlang as well. Web applications don't have to be written in ugly ad hoc languages.
Some benchmarks later, we decided to uses it for the Yakaz website, as a replacement of Apache, precisely for these reasons (and because we have some skills in Erlang).
After 7 months in production, it proves that it scales very well and that it is a very stable server. But to meet all our needs, we had to patch it to add some missing features and to fix some bugs or unexpected behaviours.
You can found here a fork of Yaws with all our updates. Feel free to get it, feedbacks are welcome.