Conference Schedule June 7, 2016
- 08:00 - 09:00 Welcome Coffee & Registration
- Be sure to arrive early and grab your favourite seat!
- 09:00 - 11:00 SESSION 1
Building Web Applications with Angular 2TIM RUFFLESDescription will be available soon.
- 11:00 - 11:30 Coffee Break
- 11:30 - 13:15 SESSION 2
PASS ME THAT FUNCTIONADRIAN GHEORGHEA talk about functional and reactive concepts and how they can simplify the arhitecture of our increasingly complex browser applications. We'll look at how these concepts can help with combining pieces of logic, keeping our code dry and make dealing with asynchronous APIs more pleasant.
INSTRUMENTING NODE.JS IN PRODUCTIONTHOMAS WATSONThis talk covers different approaches of instrumenting a Node.js application. If applied correctly, instrumentation will allow you to discover bottlenecks or track and log application usage - even in production, without sacrificing performance. Part one will cover the current state of tracing and instrumentation. In part two we’ll take a look at the next-gen core tracing API’s being developed under the Node.js Tracing Working Group.
- 13:15 - 14:15 Lunch
- Five star buffet for everybody.
- 14:15 - 16:00 SESSION 3
DATA FETCHING IN REACTFORBES LINDESAYThis talk will cover how to manage state, and how to fetch data from the server in a React application, giving you the right tools to use, regardless of the size of your application.
- 16:00 - 16:30 Coffee Break
- 16:30 - 18:15 SESSION 4
OH MY IOTSEBASTIAN GOLASCHLet`s face the truth, "The Internet of Things" (or IoT like the all the cool cats say) isn't more than a fancy buzzword. Interestingly though, it is used by two different groups of people, one wants to "shove big data into the cloud" and the other group builds DIY software & hardware to control their coffee machine using a Tessel backed up by an Raspberry PI. If we dive deeper into this topic, looking for a common ground both groups build upon, we see the same questions bubbling up: Is my battery powered motion detector really connected to the internet? If all these devices belong to the category "Internet of Things", why do I need a vendor specific access point to control them? Does my cloudy big data lightbulb producer know when I turn on the lights? And very important: Why doesn't this "Internet of Things" work in my browser? Do I really need 20 iPhone apps to turn stuff on and off? On the meta level, all these questions could be answered with: "open source"!
P2P ARCHITECTUREJAMES HALLIDAYHere are some architectural patterns and handy node modules to build distributed, peer to peer applications for node and the browser. We will cover primitives for log replication, indexing with materialized views, the properties of merkle DAGs, and some supplementary tree data structures in order to build some practical tools like a p2p key/value store, a p2p map editor, and a p2p calendar.