Giters

gocircuit / circuit

Circuit: Dynamic cloud orchestration http://gocircuit.org

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Apache STorm

opened this issue · comments

commented

This is not an issue.

I just noticed that Apache storm has the same / similar objectives.

Worth looks at the architecture.

commented

Yes. I've been aware of Apache Storm for a few years now.

Their system is for more specific purpose (mainly data processing).
Also, I doubt that Apache Storm is a zero-config. Is it?

The circuit provides full separation between the roles
of USER, DEVELOPER and (machine) PROVISIONER.
(There is no SYSADMIN or OPS engineer in the workflow anymore.
This folds back into the role of the DEVELOPER. The PROVISIONER
is the person who turns on the power switch on a new host.
circuit daemon starts on power on, like an sshd, without any
configuration.)

I hope that clarifies.

Cheers
Petar

On 30 June 2014 09:55, Gerard Webb notifications@github.com wrote:

This is not an issue.

I just noticed that Apache storm has the same / similar objectives.

Worth looks at the architecture.

—
Reply to this email directly or view it on GitHub
#6.

commented

Thanks petar

I saw the video talk you gave a gophercon.

The way you abstracted the gorotines was interesting.
Is there any actor model concurrency ?
Where is this heading ?

Ged

commented

Let me first resolve a confusion:

The CSP model and the actor model are apples and pears.
You cannot compare them.

Let me explain.

CSP is a concurrency model. Actor is a programming model.
A programming model is a concurrency model + point of view semantic.

Now in English:

The CSP model determines that you can afford multiple places
of concurrent execution (the processes) and that you can create
some communication mechanism (the channels) between them, etc.

The Actor model says how you are going to program the behavior of
a CSP environment. And the term is actually vague, because there are
two possible meanings used in industry:

(1) It can mean that the behavior of a CSP app is codified in multiple
1st-person point-of-view programs that run on each CSP process. Or,

(2) It can mean that the behavior of a CSP app is codified by a single
program with a 3rd-person (omniscient) point-of-view.

The circuit provides an API to a concurrency model (CSP) of the data center
at process level.

You can wrap it in any linguistic programming paradigm, like Actor model
for instance.

Where the circuit is headed?

The circuit is my first building block for a larger project in cognitive
science.

I have developed a new programming language, called Escher. This language
will be open-sourced later this year (I expect). But the bullet points are
that
the language involves visual programming by drawing electric-like circuits,
and
this will be the metaphor for controlling/programming data centers.

Make sense?

Thanks
P

On 30 June 2014 16:04, Gerard Webb notifications@github.com wrote:

Thanks petar

I saw the video talk you gave a gophercon.

The way you abstracted the gorotines was interesting.
Is there any actor model concurrency ?
Where is this heading ?

Ged

—
Reply to this email directly or view it on GitHub
#6 (comment).

commented

That really explains it fully.

The Escher system sounds very similar to what we are building for cognitive
science also.

Ours is a bit like grasshopper and FBP. But it has been developed into a
more narrow focus in terms of GUI.

We are planning on using go and JavaScript.
http://www.biomimicrygermany.de is our organisation.

Can we discuss over google hangout ?

Regards

Gerard webb
On 1 Jul 2014 13:46, "maymounkov" notifications@github.com wrote:

Let me first resolve a confusion:

The CSP model and the actor model are apples and pears.
You cannot compare them.

Let me explain.

CSP is a concurrency model. Actor is a programming model.
A programming model is a concurrency model + point of view semantic.

Now in English:

The CSP model determines that you can afford multiple places
of concurrent execution (the processes) and that you can create
some communication mechanism (the channels) between them, etc.

The Actor model says how you are going to program the behavior of
a CSP environment. And the term is actually vague, because there are
two possible meanings used in industry:

(1) It can mean that the behavior of a CSP app is codified in multiple
1st-person point-of-view programs that run on each CSP process. Or,

(2) It can mean that the behavior of a CSP app is codified by a single
program with a 3rd-person (omniscient) point-of-view.

The circuit provides an API to a concurrency model (CSP) of the data center
at process level.

You can wrap it in any linguistic programming paradigm, like Actor model
for instance.

Where the circuit is headed?

The circuit is my first building block for a larger project in cognitive
science.

I have developed a new programming language, called Escher. This language
will be open-sourced later this year (I expect). But the bullet points are
that
the language involves visual programming by drawing electric-like circuits,
and
this will be the metaphor for controlling/programming data centers.

Make sense?

Thanks
P

On 30 June 2014 16:04, Gerard Webb notifications@github.com wrote:

Thanks petar

I saw the video talk you gave a gophercon.

The way you abstracted the gorotines was interesting.
Is there any actor model concurrency ?
Where is this heading ?

Ged

—
Reply to this email directly or view it on GitHub
#6 (comment).

—
Reply to this email directly or view it on GitHub
#6 (comment).

commented

Yeah. Sure.

When would be a good time?

Petar

On 1 July 2014 11:16, Gerard Webb notifications@github.com wrote:

That really explains it fully.

The Escher system sounds very similar to what we are building for
cognitive
science also.

Ours is a bit like grasshopper and FBP. But it has been developed into a
more narrow focus in terms of GUI.

We are planning on using go and JavaScript.
http://www.biomimicrygermany.de is our organisation.

Can we discuss over google hangout ?

Regards

Gerard webb
On 1 Jul 2014 13:46, "maymounkov" notifications@github.com wrote:

Let me first resolve a confusion:

The CSP model and the actor model are apples and pears.
You cannot compare them.

Let me explain.

CSP is a concurrency model. Actor is a programming model.
A programming model is a concurrency model + point of view semantic.

Now in English:

The CSP model determines that you can afford multiple places
of concurrent execution (the processes) and that you can create
some communication mechanism (the channels) between them, etc.

The Actor model says how you are going to program the behavior of
a CSP environment. And the term is actually vague, because there are
two possible meanings used in industry:

(1) It can mean that the behavior of a CSP app is codified in multiple
1st-person point-of-view programs that run on each CSP process. Or,

(2) It can mean that the behavior of a CSP app is codified by a single
program with a 3rd-person (omniscient) point-of-view.

The circuit provides an API to a concurrency model (CSP) of the data
center
at process level.

You can wrap it in any linguistic programming paradigm, like Actor model
for instance.

Where the circuit is headed?

The circuit is my first building block for a larger project in cognitive
science.

I have developed a new programming language, called Escher. This language
will be open-sourced later this year (I expect). But the bullet points are
that
the language involves visual programming by drawing electric-like
circuits,
and
this will be the metaphor for controlling/programming data centers.

Make sense?

Thanks
P

On 30 June 2014 16:04, Gerard Webb notifications@github.com wrote:

Thanks petar

I saw the video talk you gave a gophercon.

The way you abstracted the gorotines was interesting.
Is there any actor model concurrency ?
Where is this heading ?

Ged

—
Reply to this email directly or view it on GitHub
#6 (comment).

—
Reply to this email directly or view it on GitHub
#6 (comment).

—
Reply to this email directly or view it on GitHub
#6 (comment).

commented

Well I I'm berlin. GMT+2

Anytime this week during the day is ok with me. Am coding all week.

So you pick :)
On 1 Jul 2014 18:44, "maymounkov" notifications@github.com wrote:

Yeah. Sure.

When would be a good time?

Petar

On 1 July 2014 11:16, Gerard Webb notifications@github.com wrote:

That really explains it fully.

The Escher system sounds very similar to what we are building for
cognitive
science also.

Ours is a bit like grasshopper and FBP. But it has been developed into a
more narrow focus in terms of GUI.

We are planning on using go and JavaScript.
http://www.biomimicrygermany.de is our organisation.

Can we discuss over google hangout ?

Regards

Gerard webb
On 1 Jul 2014 13:46, "maymounkov" notifications@github.com wrote:

Let me first resolve a confusion:

The CSP model and the actor model are apples and pears.
You cannot compare them.

Let me explain.

CSP is a concurrency model. Actor is a programming model.
A programming model is a concurrency model + point of view semantic.

Now in English:

The CSP model determines that you can afford multiple places
of concurrent execution (the processes) and that you can create
some communication mechanism (the channels) between them, etc.

The Actor model says how you are going to program the behavior of
a CSP environment. And the term is actually vague, because there are
two possible meanings used in industry:

(1) It can mean that the behavior of a CSP app is codified in multiple
1st-person point-of-view programs that run on each CSP process. Or,

(2) It can mean that the behavior of a CSP app is codified by a single
program with a 3rd-person (omniscient) point-of-view.

The circuit provides an API to a concurrency model (CSP) of the data
center
at process level.

You can wrap it in any linguistic programming paradigm, like Actor model
for instance.

Where the circuit is headed?

The circuit is my first building block for a larger project in cognitive
science.

I have developed a new programming language, called Escher. This
language
will be open-sourced later this year (I expect). But the bullet points
are
that
the language involves visual programming by drawing electric-like
circuits,
and
this will be the metaphor for controlling/programming data centers.

Make sense?

Thanks
P

On 30 June 2014 16:04, Gerard Webb notifications@github.com wrote:

Thanks petar

I saw the video talk you gave a gophercon.

The way you abstracted the gorotines was interesting.
Is there any actor model concurrency ?
Where is this heading ?

Ged

—
Reply to this email directly or view it on GitHub
#6 (comment).

—
Reply to this email directly or view it on GitHub
#6 (comment).

—
Reply to this email directly or view it on GitHub
#6 (comment).

—
Reply to this email directly or view it on GitHub
#6 (comment).