Zohaib Ijaz mzohaibqc

S3 Static Sites

⚠ This post is fairly old. I don't keep it up to date. Be sure to see comments where some people have posted updates

What this will cover

GraphQL is awesome. I was not a fan at first, but I have since been converted. I wouldn't hesitate to use it for anything new. Its not perfect though.
Running on Lambda is pretty straight forward. We have our own custom code for that, but if I was starting fresh, I would use the Apollo GraphQL server. They have one that is designed to run on Lambda. I've played with it and it works well.
If your graphQL resolvers are talking directly to a DB, make sure to share connections between requests. One connection per lambda instance. If you spin up a new connection per request you will have a bad time. I guess this is generally true for not-graphql lambda things too.
You need dataloader. It will batch DB queries for you. It (or something like it) is pretty critical to making any graphQL setup performant. Or at least not overload your DB.
You proabably need to follow the Relay spec. We didn't d

	import os
	from log_exceptions import log_exceptions

	def throw_something(a1, a2):
	raise Exception('Whoops!')

	@log_exceptions(log_if = os.getenv('MYAPP_DEBUG') is not None)
	def my_function(arg1, arg2):
	throw_something(arg1 + 24, arg2 - 24)

	import React, { PropTypes } from 'react';
	import Select from 'react-select';
	import 'react-select/dist/react-select.css';

	RFReactSelect.defaultProps = {
	multi: false,
	className: ""
	};

	RFReactSelect.propTypes = {

	# Search for `analytics` only inside `./src/app`
	git grep analytics -- "./src/app/*"