clustering #173

Open
ghost opened this Issue Dec 3, 2012 · 9 comments

Projects

None yet

1 participant

@ghost
ghost commented Dec 3, 2012

there is better clustering node js library that is more production friendly.

http://ql-io.github.com/cluster2/

it has draining, checking and logging and many other things needed. It is used by ebay.

also the will work with load balancers properly also as it has health checking.

@richtera
Collaborator
richtera commented Dec 3, 2012

I'll check it out. We had major problems with cluster due to hook.io when
moving to the node builtin clustering. I am not sure if there would be
similar conflicts with cluster2 but it looks ok.
Thanks
Andy

Sent via the internets

On Dec 3, 2012, at 7:42 AM, Gerard Webb notifications@github.com wrote:

there is better clustering node js library that is more production friendly.

http://ql-io.github.com/cluster2/

it has draining, checking and logging and many other things needed. It is
used by ebay.

also the will work with load balancers properly also as it has health
checking.


Reply to this email directly or view it on
GitHubhttps://github.com/cliftonc/calipso/issues/173.

@ghost
ghost commented Dec 3, 2012

yeah its quality i think. Also has nice set-up for proxy.

we should asks what proxy they use too. Might be a nodejs one too

g

On 3 December 2012 14:32, Andreas Richter notifications@github.com wrote:

I'll check it out. We had major problems with cluster due to hook.io when
moving to the node builtin clustering. I am not sure if there would be
similar conflicts with cluster2 but it looks ok.
Thanks
Andy

Sent via the internets

On Dec 3, 2012, at 7:42 AM, Gerard Webb notifications@github.com wrote:

there is better clustering node js library that is more production
friendly.

http://ql-io.github.com/cluster2/

it has draining, checking and logging and many other things needed. It is
used by ebay.

also the will work with load balancers properly also as it has health
checking.


Reply to this email directly or view it on
GitHubhttps://github.com/cliftonc/calipso/issues/173.


Reply to this email directly or view it on GitHubhttps://github.com/cliftonc/calipso/issues/173#issuecomment-10952653.

+46 73 364 67 96

@ghost
ghost commented Dec 3, 2012

hook.io looks awesome. did not know this existed for nodejs.
Curious where this is used in calipso ?

On 3 December 2012 14:38, Ged Wed gedw99@gmail.com wrote:

yeah its quality i think. Also has nice set-up for proxy.

we should asks what proxy they use too. Might be a nodejs one too

g

On 3 December 2012 14:32, Andreas Richter notifications@github.comwrote:

I'll check it out. We had major problems with cluster due to hook.iowhen
moving to the node builtin clustering. I am not sure if there would be
similar conflicts with cluster2 but it looks ok.
Thanks
Andy

Sent via the internets

On Dec 3, 2012, at 7:42 AM, Gerard Webb notifications@github.com
wrote:

there is better clustering node js library that is more production
friendly.

http://ql-io.github.com/cluster2/

it has draining, checking and logging and many other things needed. It is
used by ebay.

also the will work with load balancers properly also as it has health
checking.


Reply to this email directly or view it on
GitHubhttps://github.com/cliftonc/calipso/issues/173.


Reply to this email directly or view it on GitHubhttps://github.com/cliftonc/calipso/issues/173#issuecomment-10952653.

+46 73 364 67 96

+46 73 364 67 96

@richtera
Collaborator
richtera commented Dec 3, 2012

All events are published through hook.io but there is work to be done to
actually make that useful :)
Andy

Sent from my iPhone

On Dec 3, 2012, at 8:41 AM, Gerard Webb notifications@github.com wrote:

hook.io looks awesome. did not know this existed for nodejs.
Curious where this is used in calipso ?

On 3 December 2012 14:38, Ged Wed gedw99@gmail.com wrote:

yeah its quality i think. Also has nice set-up for proxy.

we should asks what proxy they use too. Might be a nodejs one too

g

On 3 December 2012 14:32, Andreas Richter notifications@github.comwrote:

I'll check it out. We had major problems with cluster due to hook.iowhen
moving to the node builtin clustering. I am not sure if there would be
similar conflicts with cluster2 but it looks ok.
Thanks
Andy

Sent via the internets

On Dec 3, 2012, at 7:42 AM, Gerard Webb notifications@github.com
wrote:

there is better clustering node js library that is more production
friendly.

http://ql-io.github.com/cluster2/

it has draining, checking and logging and many other things needed. It
is
used by ebay.

also the will work with load balancers properly also as it has health
checking.


Reply to this email directly or view it on
GitHubhttps://github.com/cliftonc/calipso/issues/173.


Reply to this email directly or view it on GitHub<
https://github.com/cliftonc/calipso/issues/173#issuecomment-10952653>.

+46 73 364 67 96

+46 73 364 67 96


Reply to this email directly or view it on
GitHubhttps://github.com/cliftonc/calipso/issues/173#issuecomment-10952912.

@ghost
ghost commented Dec 3, 2012

Wow this sounds nice.

When you say all the events can you give me an example ? Sorry

Can scale out the back end to different sub systems running on different
processes or even servers ?

On 3 December 2012 15:02, Andreas Richter notifications@github.com wrote:

All events are published through hook.io but there is work to be done to
actually make that useful :)
Andy

Sent from my iPhone

On Dec 3, 2012, at 8:41 AM, Gerard Webb notifications@github.com wrote:

hook.io looks awesome. did not know this existed for nodejs.
Curious where this is used in calipso ?

On 3 December 2012 14:38, Ged Wed gedw99@gmail.com wrote:

yeah its quality i think. Also has nice set-up for proxy.

we should asks what proxy they use too. Might be a nodejs one too

g

On 3 December 2012 14:32, Andreas Richter notifications@github.comwrote:

I'll check it out. We had major problems with cluster due to
hook.iowhen
moving to the node builtin clustering. I am not sure if there would be
similar conflicts with cluster2 but it looks ok.
Thanks
Andy

Sent via the internets

On Dec 3, 2012, at 7:42 AM, Gerard Webb notifications@github.com
wrote:

there is better clustering node js library that is more production
friendly.

http://ql-io.github.com/cluster2/

it has draining, checking and logging and many other things needed. It
is
used by ebay.

also the will work with load balancers properly also as it has health
checking.


Reply to this email directly or view it on
GitHubhttps://github.com/cliftonc/calipso/issues/173.


Reply to this email directly or view it on GitHub<
https://github.com/cliftonc/calipso/issues/173#issuecomment-10952653>.

+46 73 364 67 96

+46 73 364 67 96


Reply to this email directly or view it on
GitHub<
https://github.com/cliftonc/calipso/issues/173#issuecomment-10952912>.


Reply to this email directly or view it on GitHubhttps://github.com/cliftonc/calipso/issues/173#issuecomment-10953643.

+46 73 364 67 96

@richtera
Collaborator
richtera commented Dec 3, 2012

Thing like login, logout, create, update and so on. Clifton would have more
info about this. Once the site is moved I would like to spend time
documenting stuff and making sure everything is flushed out
Andy

Sent from my iPhone

On Dec 3, 2012, at 9:13 AM, Gerard Webb notifications@github.com wrote:

Wow this sounds nice.

When you say all the events can you give me an example ? Sorry

Can scale out the back end to different sub systems running on different
processes or even servers ?

On 3 December 2012 15:02, Andreas Richter notifications@github.com wrote:

All events are published through hook.io but there is work to be done to
actually make that useful :)
Andy

Sent from my iPhone

On Dec 3, 2012, at 8:41 AM, Gerard Webb notifications@github.com wrote:

hook.io looks awesome. did not know this existed for nodejs.
Curious where this is used in calipso ?

On 3 December 2012 14:38, Ged Wed gedw99@gmail.com wrote:

yeah its quality i think. Also has nice set-up for proxy.

we should asks what proxy they use too. Might be a nodejs one too

g

On 3 December 2012 14:32, Andreas Richter notifications@github.comwrote:

I'll check it out. We had major problems with cluster due to
hook.iowhen
moving to the node builtin clustering. I am not sure if there would be
similar conflicts with cluster2 but it looks ok.
Thanks
Andy

Sent via the internets

On Dec 3, 2012, at 7:42 AM, Gerard Webb notifications@github.com
wrote:

there is better clustering node js library that is more production
friendly.

http://ql-io.github.com/cluster2/

it has draining, checking and logging and many other things needed. It
is
used by ebay.

also the will work with load balancers properly also as it has health
checking.


Reply to this email directly or view it on
GitHubhttps://github.com/cliftonc/calipso/issues/173.


Reply to this email directly or view it on GitHub<
https://github.com/cliftonc/calipso/issues/173#issuecomment-10952653>.

+46 73 364 67 96

+46 73 364 67 96


Reply to this email directly or view it on
GitHub<
https://github.com/cliftonc/calipso/issues/173#issuecomment-10952912>.


Reply to this email directly or view it on GitHub<
https://github.com/cliftonc/calipso/issues/173#issuecomment-10953643>.

+46 73 364 67 96


Reply to this email directly or view it on
GitHubhttps://github.com/cliftonc/calipso/issues/173#issuecomment-10954025.

@ghost
ghost commented Dec 3, 2012

OK so its being used to decouple the architecture rather than scale it out.

Still very nice.

I am wondering how to run the theme installer on a command line from a dev
setup. I pulled all the code so I can help with development.

I am also working out how to do the MVC client side. I imagine hook.io will
be nice for this.

I want to wrap the MVC with s index dB and then embed the whole thing with
phone gap and deploy to iPhone and Android. Will mean you can update the
cms on the server and when a mobile client is on network they get latest
data.

I think calipso looks like a good candidate for this as well ad mongo

G
On 03/12/2012 3:47 PM, "Andreas Richter" notifications@github.com wrote:

Thing like login, logout, create, update and so on. Clifton would have
more
info about this. Once the site is moved I would like to spend time
documenting stuff and making sure everything is flushed out
Andy

Sent from my iPhone

On Dec 3, 2012, at 9:13 AM, Gerard Webb notifications@github.com wrote:

Wow this sounds nice.

When you say all the events can you give me an example ? Sorry

Can scale out the back end to different sub systems running on different
processes or even servers ?

On 3 December 2012 15:02, Andreas Richter notifications@github.com
wrote:

All events are published through hook.io but there is work to be done
to
actually make that useful :)
Andy

Sent from my iPhone

On Dec 3, 2012, at 8:41 AM, Gerard Webb notifications@github.com
wrote:

hook.io looks awesome. did not know this existed for nodejs.
Curious where this is used in calipso ?

On 3 December 2012 14:38, Ged Wed gedw99@gmail.com wrote:

yeah its quality i think. Also has nice set-up for proxy.

we should asks what proxy they use too. Might be a nodejs one too

g

On 3 December 2012 14:32, Andreas Richter notifications@github.comwrote:

I'll check it out. We had major problems with cluster due to
hook.iowhen
moving to the node builtin clustering. I am not sure if there would
be
similar conflicts with cluster2 but it looks ok.
Thanks
Andy

Sent via the internets

On Dec 3, 2012, at 7:42 AM, Gerard Webb notifications@github.com
wrote:

there is better clustering node js library that is more production
friendly.

http://ql-io.github.com/cluster2/

it has draining, checking and logging and many other things needed.
It
is
used by ebay.

also the will work with load balancers properly also as it has health
checking.


Reply to this email directly or view it on
GitHubhttps://github.com/cliftonc/calipso/issues/173.


Reply to this email directly or view it on GitHub<
https://github.com/cliftonc/calipso/issues/173#issuecomment-10952653>.

+46 73 364 67 96

+46 73 364 67 96


Reply to this email directly or view it on
GitHub<
https://github.com/cliftonc/calipso/issues/173#issuecomment-10952912>.


Reply to this email directly or view it on GitHub<
https://github.com/cliftonc/calipso/issues/173#issuecomment-10953643>.

+46 73 364 67 96


Reply to this email directly or view it on
GitHub<
https://github.com/cliftonc/calipso/issues/173#issuecomment-10954025>.


Reply to this email directly or view it on GitHubhttps://github.com/cliftonc/calipso/issues/173#issuecomment-10955812.

@richtera
Collaborator
richtera commented Dec 7, 2012

There is a bin folder with the calipso and calipso.cmd files. They should work normally in the git clone. Is there a nodejs solution for non-jailbroken iOS?

@ghost
ghost commented Dec 7, 2012

Yes i know, but running them on a development root does not work.

Misunderstand the question. No i dont need to use nodejs on Iphone. What i
am talking about is running some of the callipso JavaScript cod in the
browser.
The intent is to have a CMS that can run offline
The advantage is that you can then upload a HTml5 app wrapping in a app
container, and never have to push it through app store again.
Just update the server side configuration through admin, and when the users
IPhone is next time connected to the network, will update itself.

This is a very powerful solution, and there is as far as i know no other
solution dong this.

Calipso having a good base as a nodeJS CMS is a good candidate fr this and
i m trying to see if others believe in this idea, and could comment about
easily this can be done based on their intimate knowledge of the
architecture.

I am new to calipso and so its had to comment fully. But i can see the code
is well decoupled and so think that what i am talking about is possible.

On 7 December 2012 02:17, Andreas Richter notifications@github.com wrote:

There is a bin folder with the calipso and calipso.cmd files. They should
work normally in the git clone. Is there a nodejs solution for
non-jailbroken iOS?


Reply to this email directly or view it on GitHubhttps://github.com/cliftonc/calipso/issues/173#issuecomment-11114358.

+46 73 364 67 96

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment