Explore >> Select a destination
|
You are here 
|
rethinkdb.com | ||
| | | | |
etcd.io
|
|
| | | | | This is an adaptation of a page previously found in the Platforms section of the documentation which described etcd deployments on various platform services. The original page was authored by Caleb Miles and others. This post provides an introduction to design considerations when designing an etcd deployment on AWS EC2 and how AWS specific features may be utilized in that context. Also, this post assumes operational knowledge of Amazon Web Services (AWS), specifically Amazon Elastic Compute Cloud (EC2). | |
| | | | |
timilearning.com
|
|
| | | | | My notes from the second chapter of Martin Kleppmann's book: Designing Data Intensive Applications. | |
| | | | |
stepchange.work
|
|
| | | | | In this post, we explore the limits of single-node Postgres and what optimizations can extend its usefulness as a primary application database before requiring more advanced scaling solutions. Monolithic ecommerce app on RDS PostgreSQL Let's use a real-world scenario, a monolith web application that uses PostgreSQL as the application database running on AWS RDS. The RDS instance is a 2xlarge. The resources are: * 8 vCPUs * 64 GB Memory * 20,000 Max I/O operations per second (IOPS) In ou | |
| | | | |
tokio.rs
|
|
| | | Tokio is a runtime for writing reliable asynchronous applications with Rust. It provides async I/O, networking, scheduling, timers, and more. | ||
