<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Books on The Edge Cases</title>
    <link>https://www.kylestratis.com/tags/books/</link>
    <description>Recent content in Books on The Edge Cases</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>© 2025</copyright>
    <lastBuildDate>Fri, 18 Sep 2026 22:38:55 -0400</lastBuildDate>
    <atom:link href="https://www.kylestratis.com/tags/books/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Designing Machine Learning Systems</title>
      <link>https://www.kylestratis.com/notes/designing-machine-learning-systems/</link>
      <pubDate>Wed, 04 Oct 2023 00:41:17 +0000</pubDate>
      <guid>https://www.kylestratis.com/notes/designing-machine-learning-systems/</guid>
      <description>&lt;p&gt;[author: Chip Huyen]&lt;/p&gt;&#xA;&lt;h2 id=&#34;summary&#34;&gt;Summary&lt;/h2&gt;&#xA;&lt;p&gt;What are the key ideas?&#xA;How can I apply this knowledge that I learned?&#xA;How do these ideas relate to what I already know?&lt;/p&gt;&#xA;&lt;h2 id=&#34;ideas&#34;&gt;💡Ideas&lt;/h2&gt;&#xA;&lt;p&gt;Note: These should become Project Idea fleeting notes with a link back to this source.&lt;/p&gt;&#xA;&lt;h2 id=&#34;fleeting-notes&#34;&gt;Fleeting Notes&lt;/h2&gt;&#xA;&lt;p&gt;Note: Conceptual notes that aren&amp;rsquo;t as tied to the source material. These are fodder for processing into evergreen notes.&lt;/p&gt;&#xA;&lt;h2 id=&#34;literature-notes&#34;&gt;Literature Notes&lt;/h2&gt;&#xA;&lt;p&gt;Note: Commentary on the book or things you don&amp;rsquo;t want to forget. Maybe for use in a public mind garden. Should have a visible source reference. These are &amp;ldquo;weakly evergreen&amp;rdquo; because they&amp;rsquo;re tied heavily to a single piece. Must be in your own words. These should be processed into Evergreen notes, or used as fodder for them.&#xA;&amp;ldquo;“Literature notes”, titled after a single work and meant primarily as linkages to other more durable notes, and as targets for backlinks. I write these roughly as “outline notes,” except for someone else’s ideas.&amp;rdquo;&#xA;These should be regularly refactored into individual notes in &lt;code&gt;Sources/! Literature Notes/&lt;/code&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Machine Learning System Design Interview</title>
      <link>https://www.kylestratis.com/notes/machine-learning-system-design-interview/</link>
      <pubDate>Sat, 15 Apr 2023 02:43:54 +0000</pubDate>
      <guid>https://www.kylestratis.com/notes/machine-learning-system-design-interview/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; See here for valid statuses&lt;/p&gt;&#xA;&lt;p&gt;[author: Ali Aminian Alex Xu]&lt;/p&gt;&#xA;&lt;h2 id=&#34;summary&#34;&gt;Summary&lt;/h2&gt;&#xA;&lt;p&gt;What are the key ideas?&#xA;How can I apply this knowledge that I learned?&#xA;How do these ideas relate to what I already know?&lt;/p&gt;&#xA;&lt;h2 id=&#34;ideas&#34;&gt;💡Ideas&lt;/h2&gt;&#xA;&lt;p&gt;Note: These should become Project Idea fleeting notes with a link back to this source.&lt;/p&gt;&#xA;&lt;h2 id=&#34;fleeting-notes&#34;&gt;Fleeting Notes&lt;/h2&gt;&#xA;&lt;p&gt;Note: Conceptual notes that aren&amp;rsquo;t as tied to the source material. These are fodder for processing into evergreen notes.&lt;/p&gt;</description>
    </item>
    <item>
      <title>System Design Interview</title>
      <link>https://www.kylestratis.com/notes/system-design-interview/</link>
      <pubDate>Mon, 31 Oct 2022 03:03:50 +0000</pubDate>
      <guid>https://www.kylestratis.com/notes/system-design-interview/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; See here for valid statuses&lt;/p&gt;&#xA;&lt;p&gt;[author: ]&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-is-the-book-about&#34;&gt;What is the Book About?&lt;/h2&gt;&#xA;&lt;p&gt;&lt;strong&gt;Note&lt;/strong&gt;: See How To Read a Book&#xA;What kind of book is it?&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Non-fiction, practical book. Examples of system design interview questions.&#xA;What is the book about in 1-2 sentences at most?&lt;/li&gt;&#xA;&lt;li&gt;System design interview questions and how to answer them.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;summaries&#34;&gt;Summaries&lt;/h2&gt;&#xA;&lt;h2 id=&#34;chapter-1-scale-from-zero-to-millions-of-users&#34;&gt;Chapter 1: Scale from Zero to Millions of Users&lt;/h2&gt;&#xA;&lt;h3 id=&#34;single-server-setup&#34;&gt;Single Server Setup&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Request flow:&#xA;&lt;ol&gt;&#xA;&lt;li&gt;Users access websites through domain names, which are resolved by DNS&lt;/li&gt;&#xA;&lt;li&gt;Internet protocol (IP) address is returned to the browser.&lt;/li&gt;&#xA;&lt;li&gt;Once IP address is obtained, HTTP requests are sent directly to server&lt;/li&gt;&#xA;&lt;li&gt;The web server returns HTML pages or JSON response.&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;database&#34;&gt;Database&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Separating web/mobile traffic (web tier) from database (data tier) servers allows them to be scaled independently.&lt;/li&gt;&#xA;&lt;li&gt;Non-relational DBs might be right choice if:&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Application requires super-low latency&lt;/li&gt;&#xA;&lt;li&gt;Data are instructured&lt;/li&gt;&#xA;&lt;li&gt;You only need to serialize and deserialize data&lt;/li&gt;&#xA;&lt;li&gt;You need to store massive amount of data.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;vertical-vs-horizontal-scaling&#34;&gt;Vertical vs. Horizontal Scaling&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Vertical scaling&lt;/strong&gt; - adding more power (CPU, memories, etc.) to servers. &amp;ldquo;Scale up&amp;rdquo;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Limitations:&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Hard limit - can&amp;rsquo;t add unlimited CPU and memory&lt;/li&gt;&#xA;&lt;li&gt;No failover or redundancy&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Horizontal scaling&lt;/strong&gt; - adding more serviers to pool of resources&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;load-balancer&#34;&gt;Load Balancer&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;A &lt;strong&gt;load balancer&lt;/strong&gt; evenly distributes traffic among web servers.&lt;/li&gt;&#xA;&lt;li&gt;The load balancer communicates with web serves via private IPs.&lt;/li&gt;&#xA;&lt;li&gt;Load balancers can redirect traffic away from offline servers&lt;/li&gt;&#xA;&lt;li&gt;They also can handle rapid gains in traffic, allowing you to simply add more servers behind the load balancer to accomodate the growing traffic.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;database-replication&#34;&gt;Database Replication&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Master/slave terminology: master only handles writes, slave databases only support reads and get copies of databases from the master.&lt;/li&gt;&#xA;&lt;li&gt;Advantages&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Better performance&lt;/li&gt;&#xA;&lt;li&gt;More reliable&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;If one slave DB is available then goes offline, read operations get directed to master database&lt;/li&gt;&#xA;&lt;li&gt;If master goes offline, after some time a slave will be promoted to the new master.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;cache&#34;&gt;Cache&lt;/h3&gt;&#xA;&lt;p&gt;A &lt;strong&gt;cache&lt;/strong&gt; is a temporary storage area that stores the result of expensive responses/frequently acccesed data in memory to serve them more quickly.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Learn Functional Programming With Elixir</title>
      <link>https://www.kylestratis.com/notes/learn-functional-programming-with-elixir/</link>
      <pubDate>Thu, 19 Aug 2021 21:35:26 +0000</pubDate>
      <guid>https://www.kylestratis.com/notes/learn-functional-programming-with-elixir/</guid>
      <description>&lt;p&gt;&lt;img src=&#34;https://m.media-amazon.com/images/I/91B-u7PRbEL._SY160.jpg&#34; alt=&#34;rw-book-cover&#34;&gt;&lt;/p&gt;&#xA;&lt;h2 id=&#34;metadata&#34;&gt;Metadata&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Author: Ulisses Almeida&lt;/li&gt;&#xA;&lt;li&gt;Full Title: Learn Functional Programming With Elixir&lt;/li&gt;&#xA;&lt;li&gt;Category: #books&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;literature-notes&#34;&gt;Literature Notes&lt;/h2&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code class=&#34;language-dataview&#34; data-lang=&#34;dataview&#34;&gt;TABLE rows.file.link AS &amp;#34;Literature Note&amp;#34;, rows.file.cday AS &amp;#34;Date&amp;#34;&#xA;&#xA;FROM #note/literature AND [Learn Functional Programming With Elixir](/notes/learn-functional-programming-with-elixir/)&#xA;&#xA;GROUP BY file.link&#xA;&#xA;sort date ASCENDING&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;h2 id=&#34;summaries&#34;&gt;Summaries&lt;/h2&gt;&#xA;&lt;h3 id=&#34;chapter-1-thinking-functionally&#34;&gt;Chapter 1: Thinking Functionally&lt;/h3&gt;&#xA;&lt;p&gt;In functional programming, functions are the basic building blocks of a program, values are immutable, and the code is declarative, rather than imperative. Functions, immutability, and declarative code are the core principles of functional programming.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
