JayKan

Overview

We run multiple server processes in two data centers. Each process listens on two ports, one for HTTP and one for HTTPS. HTTPS is terminated by Apache prior to reaching node.js. HTTP goes directly from the client to node.js (through a master load balancer). We do not use clusters. We slice our physical servers into thin virtual machines running SmartOS, each with about 3GB of memory designed for a single node.js process.

Our node.js servers are hapi.js servers using the composer functionality and plugins architecture. We have three sets of plugins loaded: mobile web front end experience (single page app), legacy API reverse proxy, and monitoring.

We also serve original node.js services off another server zone which runs closed source plugins using hapi.

Analytics

JayKan

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.

---

JayKan

#RxJS 5 Operators By Example

UPDATE: I have moved the contents of this gist plus more to https://github.com/btroncone/learn-rxjs and http://www.learnrxjs.io. For expanded examples, explanations, and resources, please check out this new location!

A complete list of RxJS 5 operators with easy to understand explanations and runnable examples.

Chinese Version by: @DrakeLeung

Table of Contents

• buffer

JayKan

#Comprehensive Introduction to @ngrx/store By: @BTroncone

Also check out my lesson @ngrx/store in 10 minutes on egghead.io!

Update: Non-middleware examples have been updated to ngrx/store v2. More coming soon!

Table of Contents

JayKan

[
  {
    "name": "Secrets of the JavaScript Ninja",
    "description": "For anyone serious about web development, it's not enough to be a decent JavaScript coder. They need to be ninja-stealthy, efficient, and ready for anything. Secrets of the JavaScript Ninja, Second Edition dives below the surface and helps readers understand the deceptively-complex world of JavaScript and browser-based application development. It skips the basics, and dives into core JavaScript concepts such as functions, closures, objects, prototypes, promises, and so on.",
    "price": "21.77",
    "author": "John Resig, Bear Bibeault, and Josip Maras",
    "promoted": false,
    "tags": ["Master", "JavaScript"]
  },
  {

JayKan

var uk = createFuzzyScorer('United Kingdom');
var us = createFuzzyScorer('United States');

console.log([
  uk('United') > uk('uk'),
  uk('nited') > uk('ingdom'),
  uk('united kingdom') > uk('united kingdo'),
  uk('united dom') < uk('united kin'),
  uk('knited k') > uk('dom'),
  uk('_united_') < uk('united'),

JayKan

function git_likely_authority() {
  # Outputs a ranked list of likely author(itie)s regarding tracked files matching *${1}*
  # (Makes it easier to discover who likely knows most about the matched files)
  # (Note: Not always indicative if large refactors/renamings have occurred)
  # E.g. `git_likely_authority some_pattern_that_matches_a_path`
  git ls-files "*${1}*" |
  grep -v -E 'node_modules|vendor' | # edit to avoid certain files/dirs
  xargs -n1 git blame --line-porcelain |
  sed -n 's/^author //p' |
  sort -f |

JayKan

// ----------------------------------------------------------
// A short snippet for detecting versions of IE in JavaScript
// without resorting to user-agent sniffing
// ----------------------------------------------------------
// If you're not in IE (or IE version is less than 5) then:
//     ie === undefined
// If you're in IE (>=5) then you can determine which version:
//     ie === 7; // IE7
// Thus, to detect IE:
//     if (ie) {}

JayKan

import Layer from 'express/lib/router/layer';
const Promise = global.Promise;

/**
 * "fixt" express mbt promises. Als een stukje middleware een promise returnt dan moeten errors eigenlijk aan next worden gegeven.
 *
 * We hadden ook de suffix `Async` kunnen gebruiken om naast de bestaande functies nieuwe te maken. Dat heeft een flink nadeel
 * omdat de api op verschillende manieren te benaderen is.
 */

JayKan

3 Gripes With React

I started using React 3.5 years ago, and I still love it. It was such a well-designed solution that not much has changed since then, only superficial stuff like naming. What I learned then is still wholly applicable today because it's such a good idea (although now you can choose from many other libraries). On top of that, we now benefit from an entirely new architecture (fiber) without changing much.