Difference between revisions of "Book/Designing Data-Intensive Applications"

From PKC
Jump to navigation Jump to search
 
(7 intermediate revisions by the same user not shown)
Line 11: Line 11:


<noinclude>
<noinclude>
[[Martin Kleppmann]] teaches a course on [https://www.cl.cam.ac.uk/teaching/2021/ConcDisSys/ Distributed systems]<ref>Distributed Systems, Instructor Martin Kleppmann, [https://www.cl.cam.ac.uk/teaching/2021/ConcDisSys/ Website] [https://www.cl.cam.ac.uk/teaching/2021/ConcDisSys/dist-sys-notes.pdf course note]</ref>. The author also has a video series called [[Video/Distributed Systems|Distributed Systems]]<ref>{{:Video/Distributed Systems}}</ref> on Youtube. One may also want to read on [[Jean Bacon]]'s book on [[Book/Concurrent Systems|Concurrent Systems]]<ref>{{:Book/Concurrent Systems}}</ref>.
=Critical Insights=
{{:Quote/Unix has a uniform interface}}





Latest revision as of 10:39, 16 July 2022

Kleppmann, Martin (Mar 1, 2017). Designing Data-Intensive Applications:The Big Ideas Behind Reliable, Scalable, and Maintainable Systems. local page: O'reily Press. 


Martin Kleppmann teaches a course on Distributed systems[1]. The author also has a video series called Distributed Systems[2] on Youtube. One may also want to read on Jean Bacon's book on Concurrent Systems[3].

Critical Insights

In the Unix world, the unifrom interface that allows one program to be composed with another is files and pipes; in MapReduce, that interface is a distributed filesystem. We saw that dataflow engines add their own pipe-like data transport mechanisms to avoid materializing intermediate state to the distributed filesystem, but the initial input and final output of a job is still usually HDFS.


References

Related Pages

Author:Martin Kleppmann