mesos-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Florian Leibert <>
Subject Re: It is make sense to use memo to manage Ruby/Sinatra app?
Date Mon, 14 Oct 2013 19:03:15 GMT
Hi Ryan

I think you might be interested in looking at Marathon. Marathon allows you
to keep n instances of an application running in a cluster and will ensure
that if one of them dies, another one takes over. It also aims to solve
service discovery along the way.

If you're familiar with Play! which is the "rails of the JVM", you could
take a look at this tutorial which explains all the steps in detail: The
only difference would be that you start your ruby app instead of the play

Let me know if you have any more questions.


On Sun, Oct 13, 2013 at 9:26 PM, Ryan Chan <> wrote:

> Hello,
> We have a lot of  Ruby/Sinatra apps written in house for different
> purposes.
> As you know that Ruby limitation on threading so currently we launch a lot
> of ruby process in a single machine (with different ports) in order to
> utilize the CPU power. They are behind a AWS ELB for load balancing.
> To manage these ruby process is quite manual as some app use more
> resource, while some app use less resource, so we cannot deploy too many
> ruby process on a single machine to prevent overload, the drawback is some
> resources are wasted.
> I heard people use meso to manage Java app such as Spark, I am thinking if
> it make sense to integrate memo with my ruby app, anyone tried this before?

View raw message