We're happy to announce #DeltaLake#Rust API #Python bindings v0.5.6 which includes stateright's formal verification under 3 concurrent workers, new Azure storage backend methods, and other fixes
https://t.co/RUQGPxd1oP
We have a talk next week by @lemmster on TLA+!
Excited to host him. Do shoot your questions on this thread or post on the meetup group here
https://t.co/D5QZK3Pygu
It is very late in the PhD application season, but I recently learned of NSF funding for one of my projects. So I am looking to hire one more student starting Fall 2022 or later. Interested in cloud computing, distributed systems, and the efficiency of said systems? Contact me!
I hacked together a little website for Rust for Rustaceans over at https://t.co/vAKXkymnK6. Nothing fancy, just some quotes from reviews, updates since the book's release, known errata (which I'm sure will grow with time), and some interviews. Let me know what you think!
There's a fantastic conversation between Lamport and Roy Levin: https://t.co/HbPVx6iLEz. Highlights include the equivalence between Viewstamp Replication and Paxos (2:51:22); and how he views Raft's simplicity argument (3:05:23). It's three hours (!) but there is a transcript.
74th DistSys reading group paper was "Vewstamped Replication Revisited." This is a foundational paper with a very clear explanation of state machine replication. Arguably, it is easier to understand than Raft.
@jorandirkgreef presented the paper
Summary: https://t.co/M7yaiakwOE
@heidiann360@ChrisJe34211511 Paxos on a log is the way to go! We used an almost identical protocol for years in our distsys courses at KTH, edX and students find it much more intuitive than Raft/Multipaxos-we call it “Sequence Paxos”.
https://t.co/IhdF10MzBf
With the start of the new academic year, many students have been asking me about the best strategies for paper reading. The Shampoo Algorithm works well for me - I am not afraid of reading and rereading paragraphs and sections many times over. https://t.co/ogWgXGDTmx
A lot of software tools now use the "Four Types of Documentation" model (tutorials, how-tos, explanations, references). It's good people are formalizing the theory of docs! But the model is just a starting point— we can have a more sophisticated theory
https://t.co/aiDOuQK3e7
I've been using this format for Principal Design Reviews since I learned it from Brad Porter. Get all of the questions out and marked up (hardest part is that no-one is allowed to answer yet!), then prioritize them, then tackle them. WAY more efficient and helps avoid ratholing.