Hassy Veldstra hassy

Deploying Parse Server on AWS

Note: this is a work-in-progress and will be updated with more information over the next few days.

Intro

This guide will walk you through deploying your own instance of the open-source Parse Server. This would be a good starting point for testing your existing application to see if the functionality provided by the server is enough for your application, and to potentially plan your migration off the Parse Platform.

This guide will walk you through using Elastic Beanstalk (EB), which is an AWS service similar to Heroku. Why use EB rather than Heroku? Elastic Beanstalk does not lock you into Heroku-specific ways of doing things, is likely cheaper to run your backend on than Heroku, and it integrates with other services that AWS offer (and they offer almost everything one needs to run an application these days).

AWS API Gateway

GraphQL

Lambda

What we wanted

To recap:

20 lambdas
10 SNS topics (more than one subscriber/publisher for some)
S3 buckets (triggering lambdas)

	{
	"config": {
	"target": "http://127.0.0.1:3003",
	"phases": [
	{"duration": 30, "arrivalRate": 5}
	]
	},
	"scenarios": [
	{
	"flow": [

	{
	"config": {
	"target": "http://localhost",
	"phases": [
	{"duration": 10, "arrivalRate": 20}
	]
	},
	"scenarios": [
	{
	"flow": [

	config:
	target: "http://localhost:8080"
	phases:
	- duration: 60
	arrivalRate: 1
	processor: "./processor.js"
	scenarios:
	- name: "Load the options page"
	flow:
	- get:

	//
	// Lambda's timeout needs to be >5 seconds, 10 should do
	//

	var startedAt = new Date();

	var interval = setInterval(function () {
	console.log(startedAt, new Date());
	}, 1000);

	- post:
	url: "/some/url"
	formData:
	firstName: "Jerry"
	lastName: "Winston"
	headers:
	authorization: "Bearer {{access_token}}"

	node server.js

	# npm install artillery
	./node_modules/.bin/artillery run large_payload.json

	config:
	target: "http://localhost:3003"
	phases:
	- duration: 1
	arrivalRate: 1
	scenarios:
	- flow:
	- get:
	url: "/"
	- get: