<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Scalability on Fabio Oliveira</title><link>https://fbdo.github.io/tags/scalability.html</link><description>Recent content in Scalability on Fabio Oliveira</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 27 Jan 2019 20:53:16 +0100</lastBuildDate><atom:link href="https://fbdo.github.io/tags/scalability/index.xml" rel="self" type="application/rss+xml"/><item><title>Scalability and high availability rules</title><link>https://fbdo.github.io/posts/scalability-and-high-availability-rules.html</link><pubDate>Sun, 27 Jan 2019 20:53:16 +0100</pubDate><guid>https://fbdo.github.io/posts/scalability-and-high-availability-rules.html</guid><description>&lt;h1 id="objectives"&gt;
 Objectives
 &lt;a class="heading-link" href="#objectives"&gt;
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"&gt;&lt;/i&gt;
 &lt;span class="sr-only"&gt;Link to heading&lt;/span&gt;
 &lt;/a&gt;
&lt;/h1&gt;
&lt;p&gt;This page describes a set of rules and a methodology that, once applied to a system, can help you evaluate how well your system is regarding
scalability and availability, can help you map your weaknesses and plan actions to improve them.
In this context, scalability, availability and performance measured by low latency and high throughput are highly intertwined, as a high available
system need to scale to be available regardless the load, a system with a high throughput scale more easily than one with a low throughput, and
as a consequence is more available.&lt;/p&gt;</description></item></channel></rss>