Ashley Raiteri ashrocket

System Design Resiliency Cards

Card 1: Scalability

Design for horizontal scaling to handle increased load.
Implement load balancing to evenly distribute traffic across servers.
Use sharding or partitioning to manage large datasets.

System Design

It Depends. On What? Tradeoffs

Question

Clarify Problem, Scope, Requirements use cases, who & how? in what sequence of events will users act Traffic, transactions per second at each bottleneck. request types, read v writes Application profiles, cpu, memory intensive, idempotency stateless, stick sessions

High Level Design

Load Balancing & CDNs

This totally happened, y'all can stop +1ing this now. GitHub Blog post. Direct link to settings where you can set this.

#Per-organization / per-repo email overrides - A feature suggestion

Here the concepts "organization" and "user" are interchangeable, I'm talking about an entity that owns a repo, whether it is jQuery or John Resig. I'll stick to using organization as it best represents my original use-case.

##TL;DR

	# These are here to help the IDE recognise AWS types.
	#
	# Place this file outside the 'schema' directory so are not pushed to AWS,
	# but are still picked up by PhpStorm's GraphQL plugin to help
	# validate schemas.
	#
	# https://docs.aws.amazon.com/appsync/latest/devguide/scalars.html
	#
	scalar AWSDateTime
	scalar AWSDate

	packages:
	yum:
	git: []
	htop: []

	# Install Git needed for Git based gems
	packages:
	yum:
	git: []