Live data from Hacker News

Simplify Service Dependencies with Nodes

blog.twitter.com

11–20 of 60 posts

Re: Simplify Service Dependencies with Nodes

#11

Earlier quoted context omitted.

You can execute that kind of task with a RETE engine: https://en.wikipedia.org/wiki/Rete_algorithm

Is there something more general?

I've wondered about this as well. I'd want to cover ZDDs in addition to Rete (forward and back chaining).

https://en.wikipedia.org/wiki/Zero-suppressed_decision_diagr...

Re: Simplify Service Dependencies with Nodes

#12

Earlier quoted context omitted.

You can execute that kind of task with a RETE engine: https://en.wikipedia.org/wiki/Rete_algorithm

Is there something more general?

What do you mean by more general? Data in nodes in the RETE algorithm can be anything.

I highly recommend reading "Production Matching for Large Learning Systems"[0] as it was accessible enough for me to try to make a basic RETE implementation while learning C++ and playing around with several other technologies I was unfamiliar with[1].

[0]http://reports-archive.adm.cs.cmu.edu/anon/1995/CMU-CS-95-11...

[1]https://github.com/cjslep/cpp-rete-prototype (awful, abandoned prototype)

Re: Simplify Service Dependencies with Nodes

#13
post #10

Earlier quoted context omitted.

You can execute that kind of task with a RETE engine: https://en.wikipedia.org/wiki/Rete_algorithm

> Rete algorithm (/ˈriːtiː/ REE-tee or /ˈreɪtiː/ RAY-tee, rarely /ˈriːt/ REET or /rɛˈteɪ/ re-TAY) I guess we all can at least agree that there is a way to pronounce it :)

The first two forms are more correct, but the last two sound better. I say 'REET networks', so that's almost certainly wrong.

Re: Simplify Service Dependencies with Nodes

#14
post #13
post #10

Earlier quoted context omitted.

> Rete algorithm (/ˈriːtiː/ REE-tee or /ˈreɪtiː/ RAY-tee, rarely /ˈriːt/ REET or /rɛˈteɪ/ re-TAY) I guess we all can at least agree that there is a way to pronounce it :)

The first two forms are more correct, but the last two sound better. I say 'REET networks', so that's almost certainly wrong.

The name seems to come from Latin and courtesy to my native Romanian aka "Slavicized Latin", it should be pronounced: reh-teh, short sounds for both syllables.

Of course, since now it's a loanword in English, you could also just use English rules for pronouncing it (whichever those are :) ).

Re: Simplify Service Dependencies with Nodes

#17
post #14
post #13

Earlier quoted context omitted.

The first two forms are more correct, but the last two sound better. I say 'REET networks', so that's almost certainly wrong.

The name seems to come from Latin and courtesy to my native Romanian aka "Slavicized Latin", it should be pronounced: reh-teh, short sounds for both syllables. Of course, since now it's a loanword in English, you could also just use English rules for pronouncing it (whichever those are :) ).

Thanks - I'll try it out. You're correct that the term comes directly from Latin.

Re: Simplify Service Dependencies with Nodes

#19

Stream processing, ladies and gentlemen! Kafka Streams, Apache Beam, and everything else. Great to see so many people publishing their results for the problems addressed here.

there are not doing the stream processing are they ? this is still lots of request / response.

Re: Simplify Service Dependencies with Nodes

#20
post #19

Stream processing, ladies and gentlemen! Kafka Streams, Apache Beam, and everything else. Great to see so many people publishing their results for the problems addressed here.

there are not doing the stream processing are they ? this is still lots of request / response.

they are doing stream processing inside the same process.
Post reply on HN