Pitfalls when writing custom Frameworks

Hi everybody, I would like to assess the effort required to write a custom framework. Background: We have an application where we can start a flexible number of long-running worker processes performing number-crunching. The more processes the better. However, we have multiple users, each running

Re: Pitfalls when writing custom Frameworks

I am tempted to say that the short answer is, if your option B works, why bother writing your own scheduler/framework? Writing a Mesos framework can be easy. However, writing a fault tolerant Mesos framework that has good scalability, is performant, and is highly available can be relatively hard.

Re: Pitfalls when writing custom Frameworks

I'll echo Sharma's points. While it seems simple enough to see which moving parts you need to implement here, the long-term effort is large. I've been working on Aurora for 4.5 years, and still know of a lot of work we need to do. If your use case can fit into an existing framework (perhaps mod

Re: Pitfalls when writing custom Frameworks

Thanks Sharma and Bill! This is exactly the input I was looking for. We will start by using an existing service scheduler and see where this leads us. Best Regards, Stephan On Di, 2014-09-02 at 10:14 -0700, Bill Farner wrote: > I'll echo Sharma's points. While it seems simple enough to see whi