cmeiklejohn

11 ms·

61.
by cmeiklejohn 9y ago
Unfortunately, popular opinion disagrees and that's part of the motivation for this work.
62.
by cmeiklejohn 9y ago
Care to extrapolate? We tried hard to take industry use cases.
63.
by cmeiklejohn 9y ago
If you actually read the paper, we talk about ASN.1 and why it's insuffient for what we are doing. That's clearly stated, and it's clear you didn't read that paragraph.
64.
by cmeiklejohn 9y ago
Why sad?
65.
by cmeiklejohn 9y ago
To be fair, all modern RPC frameworks like Thrift, Protobuffs, etc. all use a IDL and it would be remiss to discount CORBA for this.
66.
by cmeiklejohn 9y ago
Just like RMI, CORBA was fine if you knew the boundaries where distribution started/ended. The issue with CORBA was the transparency and was apparent since NFS. If you used CORBA tastefully, it was fine.
67.
by cmeiklejohn 9y ago
Can you extrapolate on this?
68.
by cmeiklejohn 9y ago
As much as I disagree with CORBA, as highlighted by my publication history, it's clear in many cases it was very successful in industry in limited applications.
69.
by cmeiklejohn 9y ago
With the exception that these systems wouldn't have identified the type errors we highlight.
70.
Towards a Type System for Containers and AWS Lambda to Avoid Failures [pdf](christophermeiklejohn.com)
180 points by cmeiklejohn 9y ago|63 comments
71.
The Red Wedding Problem: Write Spikes at the Edge and a Mitigation Strategy [pdf](christophermeiklejohn.com)
86 points by cmeiklejohn 9y ago|8 comments
72.
by cmeiklejohn 9y ago
The Lasp programming system also has an eventually consistent key-value store built-in (and, we've scaled it to 1,024+ nodes). Project home: https://lasp-lang.readme.io/docs Results on scaling: https://arxiv
73.
by cmeiklejohn 9y ago
Thanks for the feedback.
74.
by cmeiklejohn 9y ago
Good point. But, most of the post was meant as joke to see what I could push lambda to do.
75.
Stateful Experiments on AWS Lambda(christophermeiklejohn.com)
165 points by cmeiklejohn 9y ago|14 comments
76.
Necessity Is the Mother of Invention: Stateful Experiments on AWS Lambda(christophermeiklejohn.com)
4 points by cmeiklejohn 9y ago|0 comments
77.
Distinguishing Lasp from Bloom^L: Programming System vs. Programming Model(christophermeiklejohn.com)
6 points by cmeiklejohn 9y ago|0 comments
78.
Partisan: Enabling Cloud-Scale Erlang Applications(arxiv.org)
88 points by cmeiklejohn 9y ago|7 comments
79.
Playing with Lasp and CRDTs(marianoguerra.org)
104 points by cmeiklejohn 9y ago|9 comments
80.
by cmeiklejohn 9y ago
(committer on Antidote, Riak and Lasp) We're investigating a backend that works on LevelDB and RocksDB. We just haven't had the academic resources to get it implemented yet. However, it's largely an engineering resource pro
81.
by cmeiklejohn 9y ago
See my comment above that you specifically replied to. Lasp [in high-scalability mode] does not connect in a mesh, and the links I provided demonstrate that we do not connect in a mesh. I specifically provided a link in the comment [with a
82.
by cmeiklejohn 9y ago
(former Basho engineer and committer on Riak and Antidote) No, it's not Riak. [Full disclosure: work was started in 2013/2014, with Basho, as an alternative to Riak and shares Riak Core as a base. At the time, Basho was a membe
83.
by cmeiklejohn 9y ago
Ah, we might be pulling a branch for our Riak Core work. I can look into it tomorrow and get back to you.
84.
by cmeiklejohn 9y ago
I wouldn't say "better"; I'd probably say that the memory profile would be completely different. It all depends on the number of actors, the size of objects, and the workload. Remember: for large binary objects, refere
85.
by cmeiklejohn 9y ago
I suggest that you build on top of the Riak Core from Heinz Gies. That's what we are using in some of our new projects.
86.
by cmeiklejohn 9y ago
(committer on Antidote, author of Lasp, both SyncFree projects) Antidote is designed for DC deployments, in the hundreds of clusters. It provides causal consistency and transactions. Lasp is designed for high-churn, edge deployments (with
87.
by cmeiklejohn 9y ago
(committer here) It uses Riak Core as the underlying distribution layer, which is the same that Riak itself uses. For storage of the log, the built-in Erlang disk_log is used.
88.
by cmeiklejohn 9y ago
Further follow-up: we're (members of the SyncFree consortium and it's follow up project for moving CRDTs, Antidote, and Lasp to the edge) considering raising money to industrialize Antidote (and it's associated tool chain) fo
89.
by cmeiklejohn 9y ago
Here's links to other things in the SyncFree group. Lasp (previously on HN): https://news.ycombinator.com/item?id=14300763 https://news.ycombinator.com/item?id=15444156 SyncFree project review results:
90.
by cmeiklejohn 9y ago
Member of the SyncFree Consortium (and committer to Antidote) here. Here's a video from J On The Beach this year on the details around the Just-Right Consistency approach that might help answer some questions: https://www.yo

More ›