Aakash Gajjar akash-gajjar

Building a Maintainable, Agile Architecture for Realtime, Transactional Apps

A maintainable application architecture requires that the UI only contain the rendering logic and execute queries and mutations against the underlying data model on the server. A maintainable architecture must not contain any logic for composing "app state" on the client as that would necessarily embed business logic in the client. App state should be persisted to the database and the client projection of it should be composed in the mid tier, and refreshed as mutations occur on the server (and after network interruption) for a highly interactive, realtime UX.

With GraphQL we are able to define an easy-to-change application-level data schema on the server that captures the types and relationships in our data, and wiring it to data sources via resolvers that leverage our db's own query language (or data-oriented, uniform service APIs) to resolve client-specified "queries" and "mutations" against the schema.

We use GraphQL to dyn

A curated list of AWS resources to prepare for the AWS Certifications

A curated list of awesome AWS resources you need to prepare for the all 5 AWS Certifications. This gist will include: open source repos, blogs & blogposts, ebooks, PDF, whitepapers, video courses, free lecture, slides, sample test and many other resources.

Setting up Babel and nodemon

Inital set-up

Set up project:

mkdir project
cd project
npm init -y

Render 1	Render 2	State Preserved?
`<>...</>`	`<>{[...]}</>`	yes (in any level)
`<><>...</></>`	`<>...</>`	no
`[...]`	`[[...]]`	no
`[<>...</>]`*	`[...]`	no
`[<>...</>]`*	`<>...</>`	no
`[<>...</>]`*	`<>[...]</>`	no
`[<>...</>]`*	`[[...]]`	yes
`[<>...>]`*	`<><>...>>`	yes

How we incorporate next and cloudfront (2018-04-21)

Feel free to contact me at [email protected] or tweet at me @statisticsftw

This is a rough outline of how we utilize next.js and S3/Cloudfront. Hope it helps!

It assumes some knowledge of AWS.

	/**
	* Making a spiral of size N x N and output the drawing out to the console.
	* For example, when n = 10, this is how the output spiral will look like:

	* * * * * * * * *
	* *
	* * * * * * *
	* * * *
	* * * * *
	* * * * * *

	#!/bin/sh

	# Make sure to:
	# 1) Name this file `backup.sh` and place it in /home/ubuntu
	# 2) Run sudo apt-get install awscli to install the AWSCLI
	# 3) Run aws configure (enter s3-authorized IAM user and specify region)
	# 4) Fill in DB host + name
	# 5) Create S3 bucket for the backups and fill it in below (set a lifecycle rule to expire files older than X days in the bucket)
	# 6) Run chmod +x backup.sh
	# 7) Test it out via ./backup.sh

	FROM node:8.6.0-alpine
	LABEL maintainer="https://github.com/verdaccio/verdaccio"

	RUN apk --no-cache add openssl && \
	wget -O /usr/local/bin/dumb-init https://github.com/Yelp/dumb-init/releases/download/v1.2.0/dumb-init_1.2.0_amd64 && \
	chmod +x /usr/local/bin/dumb-init

	# If you want "dokku enter" don't forget install bash
	# https://github.com/dokku/dokku/issues/2572
	RUN apk update && \

	#!/bin/bash

	# mongo-backup.sh
	# Script to automate MongoDB Backups
	#
	# Requirements:
	# mongodump
	# s3cmd
	#
	# Author:

	#
	# This is the default config file. It allows all users to do anything,
	# so don't use it on production systems.
	#
	# Look here for more config file examples:
	# https://github.com/verdaccio/verdaccio/tree/master/conf
	#

	# path to a directory with all packages
	storage: ./storage

Aakash Gajjar akash-gajjar

Building a Maintainable, Agile Architecture for Realtime, Transactional Apps

Setting up Babel and nodemon

Inital set-up

How we incorporate next and cloudfront (2018-04-21)

Goals