dschenkelman

const express = require('express')
const jwt = require('express-jwt');
const dotenv = require('dotenv');
const constants = require('./constants');
const sandcastle = require('sandcastle');

dotenv.config();
const app = express()
const port = constants.PORT

dschenkelman

import * as Rx from 'rx';

const kSubject = Symbol('subject');

export default class EventAggregator {
  constructor(){
    this[kSubject] = new Rx.Subject();
  }

  publish(event, payload){

dschenkelman

The prep-script.sh will setup the latest Node and install the latest perf version on your Linux box.

When you want to generate the flame graph, run the following (folder locations taken from install script):

sudo sysctl kernel.kptr_restrict=0
# May also have to do the following:
# (additional reading http://unix.stackexchange.com/questions/14227/do-i-need-root-admin-permissions-to-run-userspace-perf-tool-perf-events-ar )
sudo sysctl kernel.perf_event_paranoid=0

dschenkelman

Keybase proof

I hereby claim:

• I am dschenkelman on github.
• I am yenkel (https://keybase.io/yenkel) on keybase.
• I have a public key whose fingerprint is 6955 6E57 3532 5D50 05EE FBF1 75A0 FEFD F7B4 DDAA

To claim this, I am signing this object:

dschenkelman

root@login:/home/vagrant# perf script
# ========
# captured on: Tue Nov 24 10:13:31 2015
# hostname : login
# os release : 3.13.0-57-generic
# perf version : 3.13.11-ckt21
# arch : x86_64
# nrcpus online : 4
# nrcpus avail : 4
# cpudesc : Intel(R) Core(TM) i7-4558U CPU @ 2.80GHz

dschenkelman

Index

db.{collection}.ensureIndex({ fieldA: 1, "nested.B": 1, "nested.C": 1 })

Bad query

db.{collection}.find({ fieldA: "abc", "nested.B": "123", "nested.C": "456"})

Only uses first two index fields and then individually scans all matching items for "nested.C": 1.

Good query

db.{collection}.find({ fieldA: "abc", "nested": { $elemMatch: { "B": "123", "C": "456" } })

dschenkelman

Rise of microservices

In an era were parallelism is important, it is key to take advantage of multiple processors to leverage our maximum computing power. However, most languages and VMs rely on thread pools and schedulers to manage work and assign work to machine cores, which might lead to either an excessive need for tuning or wasted resources.

In this talk I will explain why JavaScript and in particular it’s server side implementation: node.js can help take advantage of all your resources by providing a scalable infrastructure based on microservices, taking advantage of single thread processes that rely on an event loop. The demos will make use of containerization techiques using Docker to explain how these services can be easily deployed and can communicate in a cloud enviroment.

dschenkelman

async Task FetchUrls(IEnumerable<string> urls)
  foreach (var url in urls){
    await fetch(url);
  }
}

dschenkelman

using System.Reflection;
using Xamarin.Auth;

public class CustomAuth0Client : Auth0.SDK.Auth0Client {
  private const string AuthorizeUrl = "https://{0}/authorize?client_id={1}&redirect_uri={2}&response_type=token&connection={3}&scope={4}";
  private const string LoginWidgetUrl = "https://{0}/login/?client={1}&redirect_uri={2}&response_type=token&scope={3}";
  
  private readonly string domain;
  private readonly string clientId
  

dschenkelman

Perfil,Horario acceso,IP,Accesos inválidos,Clasificación
16,2,1,3,1
2,4,1,3,1
11,4,1,3,1
2,4,1,2,1
30,4,1,3,1
1,4,1,2,1
14,4,1,3,1
8,8,1,3,1
6,8,1,2,1