-
-
Save cmeiklejohn/8346377 to your computer and use it in GitHub Desktop.
| Think Distributed Systems Summer School | |
| Providence, RI | |
| Curriculum | |
| Friday (night session, open discussion) | |
| * Background, introductions | |
| * What are you working on in distributed systems? | |
| * Lightning talks on research or open problems | |
| Saturday (Theory, 8 Hours) | |
| * Why Do Distributed Systems Matter? | |
| * A Brief History of Distributed Systems | |
| * Exploring The Consensus Problem | |
| * Synchronization Free Data Structures | |
| * An Introduction To Process Algebras | |
| Sunday (Practice, 8 Hours) | |
| Distributed Systems | |
| * Riak | |
| * Cassandra | |
| * PNUTS | |
| Languages | |
| * Bloom | |
| * Erlang | |
| * Go | |
| * Rust |
I'm excited. I'd love to do algorithm implementation (e.g. consensus in bloom, or whatever) and automated theorem proving on the practice day.
this list could span an entire summer, let alone a single weekend. kingshit.
maybe embed process algebra into an entire section on concurrency in general?
I'd hope "Why do distributed systems matter?" would be in the introduction on friday, so we can get down to real business on the saturday, but maybe i'm trivialising a complex topic...
How do you LVar without Haskell? ;)
Looks great! You should do a road show and bring it here to SF as well
Any idea roughly of when you may want to do this? Hopefully not in August :)
Thinking possibly June?
Have you considered https://github.com/coreos/etcd as one of the things to study? Implemented in Go, uses Raft, not a full database but is a great example of a consensus algorithm in production.
I'm interested in learning how to think about eventual consistency from an application level, but everything else here is systems and so it feels absurdly out of place... :-/
i want in on this weekend
Looking good so far...this is such a great idea.