Wallaroo Labs Blog

Hi y'all. I'm the author of the post and will be keeping an eye on the comments this evening. Happy to answer questions as best as I can. Part 1 is available at https://blog.wallaroolabs.com/2018/04/adventures-with-cgo-part-1--the-…

While I'm not affiliated with Wallaroo Labs, I've been following their work. One of the best things to check out is their nice collection of blog articles. 1: https://blog.wallaroolabs.com/2017/03/hello-wallaroo/ has some figures around latencies their working with and https://blog.wallaroolabs.com/2017/10/measuring-correctness-of-state-i… talks about how they test their system under faults 2: https://blog.wallaroolabs.com/2017/10/why-we-used-pony-to-write-wallar… For the rest, I better leave it to them to give the most up to date answers on those as the project is moving fast.

I think that one of the great benefits to open source platforms such as PostgreSQL, Hadoop, Kafka and others is that their open license guarantees no vendor lock-in. This means users can relax in the knowledge that the platform won't disappear if the original company disappears (or hikes prices), and means that it's possible to support the platform forever - even if that means bringing it in-house. The Wallaroo license seems to be non-free, which I think is very unfortunate and a misses an opportunity to be more widely used: https://blog.wallaroolabs.com/2017/09/open-sourcing-wallaroo/#licensin…

Wallaroo Labs | Developer Evangelist | SF Bay Area | Full-time We are the makers of Wallaroo - ultrafast framework for building & operating stateful data applications without worrying about scale. Wallaroo Labs is working on a huge idea, and this is a phenomenal opportunity for a person who enjoys challenges. We believe in open source and strive to build on these technologies. Our distributed team is ten people and growing. We had have generated a lot of interest in our product and vision and raised a large seed round with several well-known VCs. We are looking for a Developer Evangelist to drive the adoption of Wallaroo open-source offering within the developer community. This position is essential to our success; you will be responsible for identifying friction points with Wallaroo and systematically eliminate to improve the developer experience. Qualities we are looking for - Ability to learn new technologies quickly. - Comfortable with a variety of programming languages, experience with Python, Go, JavaScript are a plus. - Familiar with Big Data technologies. - Desire and ability to work with enterprise clients and our open source community. - Experience working with open source software, GitHub, etc. -Familiar with software development process in a business setting. Outstanding verbal and written communication skills. Learn more about Wallaroo Corporate site: https://www.wallaroolabs.com Wallaroo Community Site: https://www.wallaroolabs.com/community Wallaroo…

Yes From 2017, https://blog.wallaroolabs.com/2017/10/why-we-used-pony-to-write-wallar…

They also have a blog post on just that: https://blog.wallaroolabs.com/2017/10/why-we-used-pony-to-write-wallar…

Strikes me as an odd choice - perhaps ideally the open source announcement should have contained a bit more of the "Hello wallaroo" post: https://blog.wallaroolabs.com/2017/03/hello-wallaroo/ It has a pretty good overview of what wallaroo is/does (I think, as someone outside/new to the project). Also: > We are planning on releasing Wallaroo as open source in April of this year. Ouch! :) Congratulations on getting it out the door - looks very interesting.

The Github page seems to have a bit more information so we changed the URL from https://blog.wallaroolabs.com/2017/09/open-sourcing-wallaroo/.

Note that I'm answering your question with two examples that would and might be considered OS's because they themselves had to implement the capability model in generic ways and with principles you might find useful in non-OS work. Especially with prevalence of things like containers, browsers, and full-on interpreters that are like mini-OS's. I have some non-OS examples, though. KeyKOS/KeySAFE was a whole, capability-based platform designed for high-security: http://www.cap-lore.com/Agorics/Library/KeyKos/keysafe/Keysafe.html Rees did a security kernel for Scheme48: http://mumble.net/~jar/pubs/secureos/secureos.html Waterkin server for web apps done with capability-secure version of Java: http://waterken.sourceforge.net DarpaBrowser was written in E language: http://www.combex.com/tech/darpaBrowser.html Pony is used for Wallaroo. It presumably uses reference capabilities: https://blog.wallaroolabs.com/2017/10/why-we-used-pony-to-write-wallar… https://tutorial.ponylang.org/capabilities/reference-capabilities.html Edited to add Cap n Proto for IPC. Thanks kentonv for reminder. Should not have forgotten! https://capnproto.org