Kulshekhar Kabra kulshekhar

In this gist I would like to describe an idea for GraphQL subscriptions. It was inspired by conversations about subscriptions in the GraphQL slack channel and different GH issues, like #89 and #411.

Conceptual Model

At the moment GraphQL allows 2 types of queries:

query
mutation

Reference implementation also adds the third type: subscription. It does not have any semantics yet, so here I would like to propose one possible semantics interpretation and the reasoning behind it.

Reposted from Qiita

For almost a year now, I've been using this "flux" architecture to organize my React applications and to work on other people's projects, and its popularity has grown quite a lot, to the point where it shows up on job listings for React and a lot of people get confused about what it is.

Why I'm tired of using and teaching flux

There are a billion explainations on the internet, so I'll skip explaining the parts. Instead, let's cut to the chase -- the main parts I hate about flux are the Dispatcher and the Store's own updating mechanism.

If you use a setup similar to the examples in facebook/flux, and you use flux.Dispatcher, you probably have this kind of flow:

Internet Scale Services Checklist

A checklist for designing and developing internet scale services, inspired by James Hamilton's 2007 paper "On Desgining and Deploying Internet-Scale Services."

http://mvdirona.com/jrh/talksandpapers/jamesrh_lisa.pdf

Basic tenets

Does the design expect failures to happen regularly and handle them gracefully?
Have we kept things as simple as possible?

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

WebSockets - An Introduction

WebSockets is a modern HTML5 standard which makes communication between client and server a lot more simpler than ever. We are all familiar with the technology of sockets. Sockets have been fundamental to network communication for a long time but usually the communication over the browser has been restricted. The general restrictions

The server used to have a permanent listener while the client (aka browser) was not designated any fixed listener for a more long term connection. Hence, every communication was restricted to the client demanding and the server responding.
This meant that unless the client requested for a particular resource, the server was unable to push such a resource to the client.
This was detrimental since the client is then forced to check with the server at regular intervals. This meant a lot of libraries focused on optimizing asynchronous calls and identifying the response of asynchronous calls. Notably t

	/*
	sample usage:
	var path = getDomPath(element);
	console.log(path.join(' > '));

	output:
	body > section:eq(0) > div:eq(3) > section#content > section#firehose > div#firehoselist > article#firehose-46813651 > header > h2 > span#title-46813651

	taken from:
	http://stackoverflow.com/questions/5728558/get-the-dom-path-of-the-clicked-a

	'use strict';

	const types = {
	[Number ] : 'number',
	[String ] : 'string',
	[Boolean] : 'boolean',
	[Object ] : 'object'
	};

	function of(...typesToCheck) {

	{
	"version": "0.1.0",

	"command": "go",
	"args": ["build"],
	"isShellCommand": true,

	"showOutput": "silent",
	"problemMatcher": {
	"owner": "go",

	//! Chain macro in Rust
	//!
	//! A typical usage is to avoid nested match expressions.
	//!
	//! Supports:
	//! - Pattern matching
	//! - Or expressions (A \| B => ...)
	//! - Guarded statements (x if <cond> => ...)
	//! - Implicit else (requires all arms to return same type)

	requests.post("https://api.mailgun.net/v2/DOMAIN/messages",
	auth=("api", "key-SECRET"),
	files={
	"attachment[0]": ("FileName1.ext", open(FILE_PATH_1, 'rb')),
	"attachment[1]": ("FileName2.ext", open(FILE_PATH_2, 'rb'))
	},
	data={"from": "FROM_EMAIL",
	"to": [TO_EMAIL],
	"subject": SUBJECT,
	"html": HTML_CONTENT