Reading the first line I thought it was about https://github.com/eclipse-capella/capella, the Foss solution for Model-Based Systems Engineering. Confusing. But now there is also a Capela with a single ‘l’ -) Great writeup Kyle, thank you!
If it's partly a marketing move to get it jepsened before release, then it worked on me.
"Like Smalltalk and other image-based languages, Capela persists program state directly, and allows programs to be modified over time. Indeed, Capela feels somewhat like an object-oriented database with stored procedures."
Derek from Capela here. Marketing was not our primary purpose, but I guess it worked out as such ;)
The primary reason for us engaging early on with Jepsen is that we care a lot about correctness, consistency and reliability, and we wanted the best in this field to establish a baseline of tests that we must make sure our platform passes before we even put it the hands of anybody.
It does indeed! This is a part of https://github.com/jepsen-io/elle, which infers totally-connected components of the transaction dependency graph. :-)
Aside from obvious Smalltalk influence, this also brings to mind Darklang (that switched to an open-source model recently [1]).
I wonder how this will pan out... very interesting to see new approaches being explored.
[1]: https://news.ycombinator.com/item?id=44290653
Reading the first line I thought it was about https://github.com/eclipse-capella/capella, the Foss solution for Model-Based Systems Engineering. Confusing. But now there is also a Capela with a single ‘l’ -) Great writeup Kyle, thank you!
If it's partly a marketing move to get it jepsened before release, then it worked on me.
"Like Smalltalk and other image-based languages, Capela persists program state directly, and allows programs to be modified over time. Indeed, Capela feels somewhat like an object-oriented database with stored procedures."
This seems exciting.
Derek from Capela here. Marketing was not our primary purpose, but I guess it worked out as such ;)
The primary reason for us engaging early on with Jepsen is that we care a lot about correctness, consistency and reliability, and we wanted the best in this field to establish a baseline of tests that we must make sure our platform passes before we even put it the hands of anybody.
does Jepsen's test software auto-generate the cool diagrams (like 3.22) or do you have to do it yourself? do you prefer any software to do that?
It does indeed! This is a part of https://github.com/jepsen-io/elle, which infers totally-connected components of the transaction dependency graph. :-)