How is Chicago Boss different from Rails/Django/Mason/CakePHP/My Favorite MVC Framework?

Chicago Boss is fully asynchronous, using one single process to handle hundreds or thousands of simultaneous requests, and thus it solves the classic c10k problem. All other web frameworks will break down and cry if you ask them to process more than a few dozen simultaneous requests on a single machine. Chicago Boss is built with Erlang, the same platform used by banks and telecoms to achieve unprecendented scalability and (no exaggeration) 99.9999999% reliability.

Fully asynchronous!? Doesn't that mean I need to write a bunch of callbacks and stuff? Shoot me now and dump my body in a river!

No callback chaos. You will write clean, synchronous, sequential code. Chicago Boss takes care of the rest.

How mature is Chicago Boss?

Chicago Boss is in the early stages of development, and is best for people looking to try out cutting-edge technology with a promising future. APIs will change, features may be broken, your car may explode when you turn the ignition, etc. Contributions are welcome!

Hey! Those don't look like regular Erlang modules in the example.

Chicago Boss uses some under-the-hood compiler magic to emulate the best features of Rails' ActiveRecord. Check out the BossRecord API for details.

Hey! That view code looks a lot like Django. Do I need Python installed or something?

Chicago Boss uses ErlyDTL, a pure-Erlang implementation of the Django Template Language. Check out the ErlyDTL Reference for details.

Hey! What's going on in the controller?

Chicago Boss's HTTP handling is built on top of MochiWeb. Check out the BossController API for details.

Does Chicago Boss support MySQL/Postgres/Ingres/CouchDB/Microsoft Excel?

One day Chicago Boss will interface with every database known to man. Right now you need the high-performance beast from the east, Tokyo Tyrant. (Download Tyrant.)

Where can I download Chicago Boss?

Stroll over to the Chicago Boss download page