mirrors
/
system-design-primer
mirror of https://github.com/donnemartin/system-design-primer.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #1 from joseiedo/master 

Tradução para "System design topics: start here" e "performance vs scalability".
pull/867/head
Geovana Silva 2024-07-15 10:15:33 -03:00 committed by GitHub
parent d2356f649d 3dacdab3b1
commit ffaf774e0c
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 37 additions and 37 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

74
README-pt-BR.md
View File

@ -97,11 +97,11 @@ Review the [Contributing Guidelines](CONTRIBUTING.md).
<br/> <br/>
</p> </p>
* [System design topics: start here](#system-design-topics-start-here) * [Tópicos de System design: comece aqui](#tópicos-de-system-design-comece-aqui)
* [Step 1: Review the scalability video lecture](#step-1-review-the-scalability-video-lecture) * [Etapa 1: Revise a aula em video sobre escalabilidade](#etapa-1-revise-a-aula-em-video-sobre-escalabilidade)
* [Step 2: Review the scalability article](#step-2-review-the-scalability-article) * [Etapa 2: Revise o artigo sobre escalabilidade](#etapa-2-revise-o-artigo-sobre-escalabilidade)
* [Next steps](#next-steps) * [Próximos passos](#próximos-passos)
* [Performance vs scalability](#performance-vs-scalability) * [Performance vs escalabilidade](#performance-vs-escalabilidade)
* [Latency vs throughput](#latency-vs-throughput) * [Latency vs throughput](#latency-vs-throughput)
* [Availability vs consistency](#availability-vs-consistency) * [Availability vs consistency](#availability-vs-consistency)
* [CAP theorem](#cap-theorem) * [CAP theorem](#cap-theorem)
@ -369,59 +369,59 @@ Check out the following links to get a better idea of what to expect:
| Design a circular array | [Contribute](#contributing) | | Design a circular array | [Contribute](#contributing) |
| Add an object-oriented design question | [Contribute](#contributing) | | Add an object-oriented design question | [Contribute](#contributing) |
## System design topics: start here ## Tópicos de System design: comece aqui
New to system design? Novo em System design?
First, you'll need a basic understanding of common principles, learning about what they are, how they are used, and their pros and cons. Primeiro, você precisará de uma compreensão básica dos princípios comuns, aprendendo o que eles são, como eles são usados e seus prós e contras.
### Step 1: Review the scalability video lecture ### Etapa 1: Revise a aula em video sobre escalabilidade
[Scalability Lecture at Harvard](https://www.youtube.com/watch?v=-W9F__D3oY4) [Aula sobre escalabilidade em Harvard](https://www.youtube.com/watch?v=-W9F__D3oY4)
* Topics covered: * Tópicos abordados:
* Vertical scaling * Escalabilidade vertical
* Horizontal scaling * Escalabilidade horizontal
* Caching * Cacheamento
* Load balancing * Balanceamento de carga (Load Balancing)
* Database replication * Replicação de banco de dados
* Database partitioning * Particionamento de banco de dados
### Step 2: Review the scalability article ### Etapa 2: Revise o artigo sobre escalabilidade
[Scalability](https://web.archive.org/web/20221030091841/http://www.lecloud.net/tagged/scalability/chrono) [Escalabilidade](https://web.archive.org/web/20221030091841/http://www.lecloud.net/tagged/scalability/chrono)
* Topics covered: * Tópicos abordados:
* [Clones](https://web.archive.org/web/20220530193911/https://www.lecloud.net/post/7295452622/scalability-for-dummies-part-1-clones) * [Clones](https://web.archive.org/web/20220530193911/https://www.lecloud.net/post/7295452622/scalability-for-dummies-part-1-clones)
* [Databases](https://web.archive.org/web/20220602114024/https://www.lecloud.net/post/7994751381/scalability-for-dummies-part-2-database) * [Bancos de dados](https://web.archive.org/web/20220602114024/https://www.lecloud.net/post/7994751381/scalability-for-dummies-part-2-database)
* [Caches](https://web.archive.org/web/20230126233752/https://www.lecloud.net/post/9246290032/scalability-for-dummies-part-3-cache) * [Caches](https://web.archive.org/web/20230126233752/https://www.lecloud.net/post/9246290032/scalability-for-dummies-part-3-cache)
* [Asynchronism](https://web.archive.org/web/20220926171507/https://www.lecloud.net/post/9699762917/scalability-for-dummies-part-4-asynchronism) * [Assíncronismo](https://web.archive.org/web/20220926171507/https://www.lecloud.net/post/9699762917/scalability-for-dummies-part-4-asynchronism)
### Next steps ### Próximos passos
Next, we'll look at high-level trade-offs: Em seguida, vamos olhar para os trade-offs (perdas e ganhos) de alto nível:
* **Performance** vs **scalability** * **Performance** vs **escalabilidade**
* **Latency** vs **throughput** * **Latência** vs **taxa de transferência**
* **Availability** vs **consistency** * **Disponibilidade** vs **consistência**
Keep in mind that **everything is a trade-off**. Lembre-se que **tudo é um trade-off**.
Then we'll dive into more specific topics such as DNS, CDNs, and load balancers. Em seguida, vamos explorar tópicos mais específicos, como DNS, CDNs e load balancers.
## Performance vs scalability ## Performance vs escalabilidade
A service is **scalable** if it results in increased **performance** in a manner proportional to resources added. Generally, increasing performance means serving more units of work, but it can also be to handle larger units of work, such as when datasets grow.<sup><a href=http://www.allthingsdistributed.com/2006/03/a_word_on_scalability.html>1</a></sup> Um serviço é **escalável** se tem um aumento de **performance** de forma proporcional aos recursos adicionados. Geralmente, aumentar o desempenho significa atender a mais unidades de trabalho, mas também pode significar lidar com unidades de trabalho maiores, como quando os conjuntos de dados crescem.<sup><a href=http://www.allthingsdistributed.com/2006/03/a_word_on_scalability.html>1</a></sup>
Another way to look at performance vs scalability: Outra maneira de olhar para performance vs escalabilidade:
* If you have a **performance** problem, your system is slow for a single user. * Se você tiver um problema de **performance**, seu sistema é lento para um único usuário.
* If you have a **scalability** problem, your system is fast for a single user but slow under heavy load. * Se você tiver um problema de **escalabilidade**, seu sistema é rápido para um único usuário, mas lento com uma alta carga de usuários.
### Source(s) and further reading ### Fonte(s) e leituras adicionais
* [A word on scalability](http://www.allthingsdistributed.com/2006/03/a_word_on_scalability.html) * [Uma palavra sobre escalabilidade](http://www.allthingsdistributed.com/2006/03/a_word_on_scalability.html)
* [Scalability, availability, stability, patterns](http://www.slideshare.net/jboner/scalability-availability-stability-patterns/) * [Escalabilidade, disponibilidade, estabilidade, padrões](http://www.slideshare.net/jboner/scalability-availability-stability-patterns/)
## Latency vs throughput ## Latency vs throughput