<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Distributed-Systems on Karpoke - Just Another Blog</title><link>http://karpoke.ignaciocano.com/tags/distributed-systems/</link><description>Recent content in Distributed-Systems on Karpoke - Just Another Blog</description><generator>Hugo -- 0.167.0</generator><language>es</language><lastBuildDate>Tue, 20 Jun 2023 22:37:31 +0100</lastBuildDate><atom:link href="http://karpoke.ignaciocano.com/tags/distributed-systems/index.xml" rel="self" type="application/rss+xml"/><item><title>Understanding Caching in Distributed Systems</title><link>http://karpoke.ignaciocano.com/2023/06/20/understanding-caching-in-distributed-systems/</link><pubDate>Tue, 20 Jun 2023 22:37:31 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2023/06/20/understanding-caching-in-distributed-systems/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Understanding Caching in Distributed Systems&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» hackernoon.com | &lt;a href="https://hackernoon.com/understanding-caching-in-distributed-systems"&gt;hackernoon.com&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Fixed Partitions</title><link>http://karpoke.ignaciocano.com/2022/08/23/fixed-partitions/</link><pubDate>Tue, 23 Aug 2022 16:58:34 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2022/08/23/fixed-partitions/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Keep the number of partitions fixed to keep the mapping of data to
partition unchanged when the size of a cluster changes.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» martinfowler.com | &lt;a href="https://martinfowler.com/articles/patterns-of-distributed-systems/fixed-partitions.html"&gt;martinfowler.com&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Top 5 Distributed System Design Patterns</title><link>http://karpoke.ignaciocano.com/2021/06/14/top-5-distributed-system-design-patterns/</link><pubDate>Mon, 14 Jun 2021 11:39:46 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2021/06/14/top-5-distributed-system-design-patterns/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Distributed applications are a staple of the modern software development
industry. They&amp;rsquo;re pivotal to&amp;hellip;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» DEV Community | &lt;a href="https://dev.to/educative/top-5-distributed-system-design-patterns-4d21"&gt;dev.to&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Distributed Systems Pattern: Low-Water Mark</title><link>http://karpoke.ignaciocano.com/2020/08/29/distributed-systems-pattern-low-water-mark/</link><pubDate>Sat, 29 Aug 2020 19:59:27 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2020/08/29/distributed-systems-pattern-low-water-mark/</guid><description>&lt;blockquote&gt;
&lt;p&gt;An index in the write-ahead log showing which portion of the log can be
discarded.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» martinfowler.com | &lt;a href="https://martinfowler.com/articles/patterns-of-distributed-systems/low-watermark.html"&gt;martinfowler.com&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Distributed Systems Pattern: Request Pipeline</title><link>http://karpoke.ignaciocano.com/2020/08/29/distributed-systems-pattern-request-pipeline/</link><pubDate>Sat, 29 Aug 2020 19:59:21 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2020/08/29/distributed-systems-pattern-request-pipeline/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Improve latency by sending multiple requests on the connection without
waiting for the response of the previous requests.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» martinfowler.com | &lt;a href="https://martinfowler.com/articles/patterns-of-distributed-systems/request-pipeline.html"&gt;martinfowler.com&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Distributed Systems Pattern: Singular Update Queue</title><link>http://karpoke.ignaciocano.com/2020/08/29/distributed-systems-pattern-singular-update-queue/</link><pubDate>Sat, 29 Aug 2020 19:59:21 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2020/08/29/distributed-systems-pattern-singular-update-queue/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Use a single thread to process requests asynchronously to maintain order
without blocking the caller.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» martinfowler.com | &lt;a href="https://martinfowler.com/articles/patterns-of-distributed-systems/singular-update-queue.html"&gt;martinfowler.com&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Distributed Systems Pattern: Segmented Log</title><link>http://karpoke.ignaciocano.com/2020/08/15/distributed-systems-pattern-segmented-log/</link><pubDate>Sat, 15 Aug 2020 11:16:01 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2020/08/15/distributed-systems-pattern-segmented-log/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Split log into multiple smaller files instead of a single large file for
easier operations.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» martinfowler.com | &lt;a href="https://martinfowler.com/articles/patterns-of-distributed-systems/log-segmentation.html"&gt;martinfowler.com&lt;/a&gt;&lt;/p&gt;</description></item><item><title>The design of CockroachDB</title><link>http://karpoke.ignaciocano.com/2016/10/02/the-design-of-cockroachdb/</link><pubDate>Sun, 02 Oct 2016 14:42:00 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2016/10/02/the-design-of-cockroachdb/</guid><description>&lt;blockquote&gt;
&lt;p&gt;CockroachDB is a distributed SQL database. The primary design goals are
scalability, strong consistency and survivability (hence the name).
CockroachDB aims to tolerate disk, machine, rack, and even datacenter
failures with minimal latency disruption and no manual intervention.
CockroachDB nodes are symmetric; a design goal is homogeneous deployment
(one binary) with minimal configuration and no required external
dependencies.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» Spencer Kimball | &lt;a href="https://github.com/cockroachdb/cockroach/blob/develop/docs/design.md"&gt;github.com&lt;/a&gt;&lt;/p&gt;</description></item><item><title>RebornDB: The next generation distributed key-value store</title><link>http://karpoke.ignaciocano.com/2015/07/08/reborndb-the-next-generation-distributed-key-value-store/</link><pubDate>Wed, 08 Jul 2015 21:34:00 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2015/07/08/reborndb-the-next-generation-distributed-key-value-store/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Redis is advanced key-value cache and store, under BSD license. It is
very fast, has many data types(String, Hash, List, Set, Sorted Set …),
uses RDB or AOF persistence and replication to guarantee data
security, and supplies many language client libraries. Most of all,
market chooses Redis. There are many companies using Redis and it has
proved its worth. Although redis is greate, it still has some
disadvantages, and the biggest one is memory limitation. Redis keeps
all data in memory, which limits the whole dataset size and lets us
save more data impossibly.&lt;/p&gt;
&lt;/blockquote&gt;</description></item></channel></rss>