Distributed Systems 1.1: Introduction

i see quite a bit of overlap between the book and his lecture series on distributed systems [VIDEO] These lectures give a more theory based approach, while the book is more based on discussing practical systems; now both are covering distributed systems as such. Now the distributed system audio course on youtube is extremely accessible (i listened to them while taking walks with our dog) The book is also great, Kleppmann is writing in a very accessible style.

Martin's writing and explanation style is truly awesome! I read his book DDIA (Designing data intensive applications) and listened to his distributed systems class lectures [1]. It was a joy learning. I wish I had him or someone like him in graduate school. I would've probably taken all his courses :-). [1] [VIDEO]

1. MIT's 6.824: Distributed Systems - [LINK] Lectures are available on Youtube. Assignments code and test runner are also available on the course page. 2. The Book Designing Data-Intensive Applications by Martin Kleppmann and the Youtube videos - [VIDEO] 3. Distributed Systems course by Lindsey Kuper - [LINK] 4. CMU's Database Systems and Advanced Database Systems by Andy Pavlo

His lectures are also on youtube: [VIDEO] I've been trying to watch snippets while also watching the MIT 6.824 lectures as well.

I think that i understand the argument, but things changed with the advent of microservices. Suddenly everything turned into a distributed system, and it is hard to cope without some understanding of the subject matter. This lecture series by Martin Kleppman has helped me quite a bit here: [VIDEO] Also see his book 'Designing Data-Intensive Applications', which is more focused on discussing practical systems.

Good resources for understanding Distributed Systems: - MIT course with Robert Morris (of Morris Worm fame): [LINK] - Martin Kleppmann (author of DDIA): [VIDEO] If you can work through the above (and DDIA), you'll have a solid understanding of the issues in Distributed System, like Consensus, Causality, Split Brain, etc. You'll also gain a critical eye of Cloud Services and be able to articulate their drawbacks (ex: did you know that replication to DynamoDB Secondary Indexes is eventually consistent? What effects can that have on your applications?)

I created a smart planner app at a similar age [1] and I'm now in my third year of university studying CS. I've also had a taste of industry from building a journal app as a freelancer [2], interning at a department of my uni [3] and interning at Wise [4]. - The whole js, css, html, react stuff sounds more like a beginner web dev bootcamp that should last a few months rather than a 3-4 year CS degree. Avoid that. - Sometimes YouTube is great. E.g., a playlist from a Cambridge lecturer [5] was immensely more valuable than the live lectures I was being delivered alongside 200+ other students. I don't think lectures are efficient but I typically have a mix of lectures + labs + coursework and now, a substantial individual project supervised by a researcher. I'm excited for the future of edtech and programs like OSSU [6] are great if the focus is purely on absorbing CS content but its limited. Something else I found is that the modules I dreaded the most and certainly wouldn't have opted into had they been optional were the ones I learned the most from. Who knew that an Interaction Design class would be so relevant for doing customer discovery in a startup. - No doubt that you can also have an income while studying. - Pick up an internship to learn from experienced software engineers. - The life experience is something I'll miss dearly, be it sports, socialising, dipping into the startup culture (We have an on campus accelerator). - I stress more about turning down jobs than worry