Skip to content

Instantly share code, notes, and snippets.

View sgriffiths's full-sized avatar
👀

Scott Griffiths sgriffiths

👀
View GitHub Profile
@sgriffiths
sgriffiths / moveright.csv
Last active February 27, 2022 00:24
Move right
Item Description
Increased User experience Tests closely match the actions expected by your users
Responding faster Teams have more involvement and ownership over the performance information thats presented back
Design hypothesis evaluated Assumptions are reflected upon and adequate action can be taken
Various performance management options Many different tools for being able to change traffic flows that can alter performance
@sgriffiths
sgriffiths / shiftleft.csv
Created February 27, 2022 00:22
shift-left
Item Description
Team cohesion Foster developer engagement and contribution
Less bugs Reduced development costs
Improved performance Detect and eliminate bottlenecks sooner
Reduced risk Find bugs and performance issues earlier
Speed up time-to-market Having more trust in your applications and infrastructure
Pro's Con's
Simulates real world conditions as closely as possible Often a integrated(shared) environment which can affect results
Integrated tests execute against multiple components at once Data is often 'test' data which could affect behaviour/results
Tools can replicate thousands (if not more) of users Replicating 'Prod' environments can be expensive
Extensive metrics/reports from tool Finding route case when diagnosing issues can be complex
Commercial Tooling can be expensive to operate item
@sgriffiths
sgriffiths / create, list and query talks
Last active March 25, 2020 00:54
Sample webapp - AWS Amplify-GraphQL
//Create:
mutation createTalk {
createTalk(input: {
name: "Full Stack React"
description: "React + Amplify to build Full Stack Apps with GraphQL"
speakerName: "Scotty G"
speakerBio: "Engineer"
}) {
id name description speakerName speakerBio
}

The idea is to have nginx installed and node installed. I will extend this gist to include how to install those as well, but at the moment, the following assumes you have nginx 0.7.62 and node 0.2.3 installed on a Linux distro (I used Ubuntu).

In a nutshell,

  1. nginx is used to serve static files (css, js, images, etc.)
  2. node serves all the "dynamic" stuff.

So for example, www.foo.com request comes and your css, js, and images get served thru nginx while everything else (the request for say index.html or "/") gets served through node.

  1. nginx listens on port 80.