notexOPENOverview
Notex/Systems/Scalability

Scalability

Always free to read

▷LESSON VIDEOOverview: ScalabilityVideo coming soon. Start with the reading below.COMING SOON

References

Overview: Scalability
  1. “Amazon Route 53,” https://aws.amazon.com/route53/
HTTP caching
  1. This is an example of the replication pattern in action.
  2. “HTTP caching,” https://developer.mozilla.org/en-US/docs/Web/HTTP/Caching
  3. “CQRS,” https://martinfowler.com/bliki/CQRS.html
  4. This is another instance of functional decomposition.
  5. “NGINX,” https://www.nginx.com/
  6. “HAProxy,” https://www.haproxy.com/
Content delivery networks
  1. “Amazon CloudFront,” https://aws.amazon.com/cloudfront/
  2. “Akamai,” https://www.akamai.com/
  3. “The Akamai Network: A Platform for HighPerformance Internet Applications,” https://groups.cs.umass.edu/ramesh/wp-content/uploads/sites/3/2019/12/The-akamai-network-a-platform-for-high-performance-internet-applications.pdf
  4. “Load Balancing at the Frontend,” https://landing.google.com/sre/sre-book/chapters/load-balancing-frontend/
  5. “Denial-of-service attack,” https://en.wikipedia.org/wiki/Denial-of-service_attack
  6. A cache hit occurs when the requested data can be found in the cache, while a cache miss occurs when it cannot.
Partitioning
  1. “Consistent Hashing and Random Trees: Distributed Caching Protocols for Relieving Hot Spots on the World Wide Web,” https://www.cs.princeton.edu/courses/archive/fall09/cos518/papers/chash.pdf
File storage
  1. “Amazon Simple Storage Service,” https://aws.amazon.com/s3/
  2. “Azure Blob Storage,” https://azure.microsoft.com/en-us/services/storage/blobs/#overview
  3. “Windows Azure Storage: A Highly Available Cloud Storage Service with Strong Consistency,” https://sigops.org/s/conferences/sosp/2011/current/2011-Cascais/printable/11-calder.pdf
  4. we discussed chain replication in Chain replication in Replication
  5. “Diving Deep on S3 Consistency,” https://www.allthingsdistributed.com/2021/04/s3-strong-consistency.html
Network load balancing
  1. “AWS Well-Architected Framework, Availability,” https://docs.aws.amazon.com/wellarchitected/latest/reliability-pillar/availability.html
  2. Another way to think about it is that by increasing the number of servers linearly, we increase the availability exponentially.
  3. “The power of two random choices,” https://brooker.co.za/blog/2012/01/17/two-random.html
  4. “Autoscaling,” https://docs.microsoft.com/en-us/azure/architecture/best-practices/auto-scaling
  5. “Implementing health checks,” https://aws.amazon.com/builders-library/implementing-health-checks/
  6. “Round-robin DNS,” https://en.wikipedia.org/wiki/Round-robin_DNS
  7. layer 4 is the transport layer in the OSI model
  8. “SREcon19 Americas - Keeping the Balance: Internet-Scale Loadbalancing Demystified,” https://www.youtube.com/watch?v=woaGu3kJ-xk
  9. “Network address translation,” https://en.wikipedia.org/wiki/Network_address_translation
  10. “Introduction to modern network load balancing and proxying,” https://blog.envoyproxy.io/introduction-to-modern-network-load-balancing-and-proxying-a57f6ff80236
  11. “Anycast,” https://en.wikipedia.org/wiki/Anycast
  12. “Equal-cost multi-path routing,” https://en.wikipedia.org/wiki/Equal-cost_multi-path_routing
  13. “Network Load Balancer,” https://aws.amazon.com/elasticloadbalancing/network-load-balancer/
  14. “Azure Load Balancer,” https://azure.microsoft.com/en-us/services/load-balancer/
  15. layer 7 is the application layer in the OSI model
  16. A SYN flood is a form of denial-of-service attack in which an attacker rapidly initiates a TCP connection to a server without finalizing the connection.
  17. “Service mesh data plane vs. control plane,” https://blog.envoyproxy.io/service-mesh-data-plane-vs-control-plane-2774e720f7fc
  18. “Service Mesh Wars, Goodbye Istio,” https://blog.polymatic.systems/service-mesh-wars-goodbye-istio-b047d9e533c7
Data storage
  1. “PostgreSQL Server Configuration, Replication,” https://www.postgresql.org/docs/14/runtime-config-replication.html
  2. “Amazon RDS Read Replicas,” https://aws.amazon.com/rds/features/read-replicas/
  3. “Multi-AZ deployments for high availability,” https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.MultiAZ.html
  4. That said, reducing storage costs isn’t the only benefit of normalization: it also helps maintain data integrity. If a piece of data is duplicated in multiple places, then to update it, we have to make sure it gets updated everywhere. In contrast, if the data is normalized, we only need to update it in one place.
  5. “Bigtable: A Distributed Storage System for Structured Data,” https://static.googleusercontent.com/media/research.google.com/en//archive/bigtable-osdi06.pdf
  6. we talked about Dynamo in Dynamo-style data stores in Coordination avoidance
  7. “AWS re:Invent 2018: Amazon DynamoDB Deep Dive: Advanced Design Patterns for DynamoDB (DAT401),” https://www.youtube.com/watch?v=HaEPXoXVf2k
  8. On the other hand, while we certainly can find ways to scale a relational database, what works on day 1 might not work on day 10 or 100.
  9. “Amazon DynamoDB,” https://aws.amazon.com/dynamodb/
  10. “AWS re:Invent 2018: Amazon DynamoDB Under the Hood: How We Built a Hyper-Scale Database (DAT321),” https://www.youtube.com/watch?v=yvBR71D0nAQ
  11. “The DynamoDB Book,” https://www.dynamodbbook.com/
  12. “Andy Pavlo — The official ten-year retrospective of NewSQL databases,” https://www.youtube.com/watch?v=LwkS82zs65g
  13. “NewSQL database systems are failing to guarantee consistency, and I blame Spanner,” https://dbmsmusings.blogspot.com/2018/09/newsql-database-systems-are-failing-to.html
  14. “CockroachDB,” https://github.com/cockroachdb/cockroach 15we talked about Spanner in NewSQL in Transactions
Caching
  1. “Cache coherence,” https://en.wikipedia.org/wiki/Cache_coherence
  2. “RocksDB,” http://rocksdb.org/
  3. “Redis,” https://redis.io/
  4. “Memcached,” https://memcached.org/
  5. “Redis cluster tutorial,” https://redis.io/topics/cluster-tutorial
Microservices
  1. “The Mythical Man-Month,” https://en.wikipedia.org/wiki/The_Mythical_Man-Month
  2. A more appropriate name for the microservices architecture is service-oriented architecture, but unfortunately, that name comes with some baggage as well.
  3. This idea is described well in John Ousterhout’s A Philosophy of Software Design, which I highly recommend.
  4. “MicroservicePremium,” https://martinfowler.com/bliki/MicroservicePremium.html
  5. “GraphQL,” https://graphql.org/
  6. “Introduction to JSON Web Tokens,” https://jwt.io/introduction
  7. “Microservices Security in Action,” https://www.manning.com/books/microservices-security-in-action
  8. “Azure API Management,” https://azure.microsoft.com/en-gb/services/api-management/
  9. “Amazon API Gateway,” https://aws.amazon.com/api-gateway/
Control planes and data planes
  1. “Control Planes vs Data Planes,” https://brooker.co.za/blog/2019/03/17/control.html
  2. “Avoiding overload in distributed systems by putting the smaller service in control,” https://aws.amazon.com/builders-library/avoiding-overload-in-distributed-systems-by-putting-the-smaller-service-in-control/
  3. This is another example of the CQRS pattern applied in practice.
  4. That said, there is still the potential to overload the control plane if it needs to juggle too many connections.
  5. “AWS re:Invent 2018: Close Loops & Opening Minds: How to Take Control of Systems, Big & Small ARC337,” https://www.youtube.com/watch?v=O8xLxNje30M
  6. That said, having a closed loop doesn’t guarantee that either, it’s merely a pre-requisite.
  7. “Designing Distributed Control Systems,” https://www.amazon.com/gp/product/1118694155
Messaging
  1. “Amazon Simple Queue Service,” https://aws.amazon.com/sqs/
  2. “Amazon SQS Standard queues,” https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/standard-queues.html
  3. This is also referred to as the competing consumer pattern, which is implemented using leader election.
  4. “Advanced Message Queuing Protocol,” https://en.wikipedia.org/wiki/Advanced_Message_Queuing_Protocol
  5. “Azure Queue Storage,” https://azure.microsoft.com/en-us/services/storage/queues/
  6. “You Cannot Have Exactly-Once Delivery Redux,” https://bravenewgeek.com/you-cannot-have-exactly-once-delivery-redux/
  7. As we will discuss in Maintainability (module 6), maintaining a service is no small feat.
KEEP EXPLORING

One note leads to another.

Back to the library →
⌕
Search across the entire library ⌘ K