Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Self Healing Code with clojure.spec

blog.cognitect.com

Post reply on HN
Print view View original

1–10 of 30 posts

Re: Self Healing Code with clojure.spec

#2

Post by eternalban »

Not intending to detract from the elegant and progressive thrust of the ideas here, when we consider software failure in context of distribution and higher level systems, we note that both CAP & impossibility results in that domain are applicable here and at best we can hope for episodic health checks and healing of distributed software systems. Specifically only at AP consensus points or CP system downtime for off-band repairs.

Re: Self Healing Code with clojure.spec

#3

Post by blueprint »

Good idea. I get that it was a demonstration of the application of spec but for a real implementation of self-healing code, in my opinion, there needs to be a way to verify that the problem the matched functions are supposed to be solving is the same instead of relying on some sort of statistical confidence via IO sampling.

Re: Self Healing Code with clojure.spec

#6

Post by Pica_soO »

Haven't we been there already? Systems that would run code, no matter what? The result was, that systems could be hacked by committing flawed code- which would execute completely different then intended without ever throwing a error message?

The Error this was, brought forth the fail early, fail loud approach?

Re: Self Healing Code with clojure.spec

#8

Post by jw- »

This seems like a very simple concept when compared with other systems using software transplants [1]. The most important thing I gleaned from this is the benefit of having 'type information' (clojure specs) available as first class data. The reason why this is so simple, which isn't a bad thing, is because clojure (and lisps) makes it easy to get metadata and work with it.

[1] http://crest.cs.ucl.ac.uk/autotransplantation/downloads/auto...

Re: Self Healing Code with clojure.spec

#9

Post by alimw »

eternalban wrote: post #2

Not intending to detract from the elegant and progressive thrust of the ideas here, when we consider software failure in context of distribution and higher level systems, we note that both CAP & impossibility results in that domain are applicable here and at best we can hope for episodic health checks and healing of distributed software systems. Specifically only at AP consensus points or CP system downtime for off-b…

Is this what happens when self-healing code starts to post on Hacker News :)
Post reply on HN