What's an openshift gear? Can it be the equivalent of a web-worker?

Question

Openshift pricing model states that you can have 3 gears in the free tier.

Other services normally explain their free tiers in number of "web workers" that you can have.

What is an openshift's gear exactly then? I know that you can install a different programming environment in each gear, but if you install the same one (let's say: ruby) in all your 3 free-tier gears, do you have 3 web-workers running at the same time? (As in: improving scalability and redundancy; are they load-balanced?)

Answer 1

{disclosure: I work as an Developer Evangelist on OpenShift}

We also put a big effort into explaining our pricing in terms developers can understand. Please look at the middle of the pricing page:

https://www.openshift.com/products/pricing

There is a section on how gears work. In that section you can see we can show what we load tested to give you a good starting point for what resources a normal Drupal application should be able to use. I find this easier than how many opteron servers I get.

Remember this is just an estimate, and your mileage may vary, but I think it is easier to understand.

We would love to see other people do load testing with other frameworks or applications and give us their feedback.

Answer 2

Gears can be thought of as equivalents to "web workers" however gears is better described as a unit (collection of resources).

In the OpenShift free tier you only have small gears (512MB memory, 1GB HDD, etc.) So the small gear is a unit of resources that you have for you to use.

https://www.openshift.com/pricing/index.html

If you want an application that scales (using the free tier), it can be done however some find it difficult as DB often get it's own GEAR, which only leaves you one remaining gear for scaling.