Skip to content
Jeremy B edited this page Sep 26, 2017 · 4 revisions

The following information is out-of-date, but kept for historical reference.

Amazon EC2 (Last Updated: 12/3/12)

Pros

  • Decent cost
  • Good scaling capabilities
  • Large level of control over the server
  • Allows use of websockets

Cons

  • Dynamically-priced (AKA lots of usage translates into lots of cost)
  • Distributing remote access to others is a bit of a pain
  • Not fully controlled by owner/lessee
  • Performance is fairly poor and inconsistent

Sidenotes

"Micro" instances are insufficient for Teletortoise; must be at least "Small". A "Small" instance managed to handle several demos, including one at CCL-All that involved more than a dozen different users connected to it.

Clever Cloud (Last Updated: 7/8/13)

Pros

  • Good scaling capabilities
  • Allows use of websockets
  • Allows use of Play

Cons

  • Cost is twice that of Linode

Sidenotes

We've yet to ever try running a server on Clever Cloud and seeing how it goes, so performance and reliability are currently unknowns.

CloudFoundry (Last Updated: 12/3/12)

Does not support websockets.

dotCloud (Last Updated: 12/3/12)

Does not support Play Framework 2.x. I'm aware of the existence of this, but it has not always proven reliable; last time I tried to use it, it repeatedly failed to deploy my application. Also, I find the long wait times for deployment and the lack of control over the server to be annoying. Currently, I'm preferring a more-configurable setup.

Heroku (Last Updated: 7/16/14)

Formerly didn't support websockets. It now does, but hasn't yet been evaluated by us.

Linode (Last Updated: 12/3/12)

Pros

  • Decent cost
  • Great performance
  • Good scaling capabilities
  • Virtually absolute control over the server
  • Easy to distribute access to others
  • Allows use of websockets

Cons

  • Jason is not a good sysadmin

NUIT (Last Updated: 12/3/12)

Pros

  • Free!
  • Great performance
  • Virtually absolute control over the server
  • Easy to distribute access to others
  • Allows use of websockets

Cons

  • Scalability of solution is unclear

Clone this wiki locally