…and the fourth iteration begins!
Adam Ulvi is presenting…
Put a Sensor On It!
Adam is a Portland native (straight out of the Simpsons) with a penchant for software and systems integration. 8-bit gamer, seasoned professional, perpertual noob. Specialization is for insects.
Learn how easy it is to create your own monitoring system! Hobbyist components and a rich ‘maker’ community puts advanced system designs well within the reach of your average software wonk. Stop planning and start building!
Our case study is ‘GroMon’, a solution for monitoring a tiny indoor lettuce garden. Our wireless sensor keeps track of temperature and humidity, if the plants get too hot or too cold then we are notified via text message.
We will discuss the design goals and architecture, as well as component selection, prototyping and debugging steps. With a little bit of programming skill and patience, anyone can build this network. Learn how to easily extend this solution for your own use.
Our stack is Node.js running on a Raspberry Pi. We connect over Bluetooth to an Arduino hosting a single sensor. All components can be purchased off-the-shelf, no soldering is required and the total cost is around $80. Code and bill of materials is available on GitHub, let’s hack!
Aron Racho is presenting…
Jive Purposeful Places SDK – A NodeJS Bromance
Ok, get ready, this description for this sessions is HUGE!
Jive Software’s latest cloud release enables 3rd party developers to easily push data marshalled from external systems of record such as Salesforce into Jive. Our aim is to publish a developer framework and API which makes it drop-dead simple — and fun — to get up-and-going from scratch, or easily integrate into an existing framework. We chose NodeJS precisely for those reasons:
- High developer adoption
- Best-in-class IDE support (IntelliJ for example)
- Native support for REST and HTTP
- Excellent package management system (NPM == maven the Good Parts)
- Tons of great libraries
- Amazing documentation, well organized, very easy to get started instantly
Our framework is built on Express, and is designed to be programmed by “convention: fill in the blanks with logic specific to your application, and as long as you’ve satisfied the contract, the framework automatically:
- Wires up routes required for configuring your integration
- Notifies your listeners for integration life cycle events (integration created; destroyed; updated, etc.)
- Executes recurrent tasks you’ve scheduled
- Handles persistence of required objects. We have support for 3 types of persistence out of the box — in-memory, file, and MondoDB.
The framework is designed for developers who want to as quickly as possible start integrating a 3rd party service with Jive, with minimum setup.
For those interested in integrating Jive into an existing NodeJS Express app, we are going to make the underlying API available to developers, allowing them finer grained control over the setup of their integration. This API will be the same one underlying the mechanics of the aforementioned framework.
For my presentation, I will be describe how we used NodeJS as the basis for this framework and API. Please note at the time of this proposal, we’ve created the framework, and are now in the process of refining the API so that it can be used independently of the framework.
Christopher Meiklejohn is presenting…
An Introduction to Functional Reactive Programming
Chris also knows a thing or three about this show… called The Wire… he could probably speak entirely in quotes solely from The Wire and still make complete sense. So throw a quote out, I bet he’ll catch it.
There is no doubt that todays web applications continue to grow in adoption, replacing their desktop counterparts in all areas of computation. Essential to their growth is their ability to provide near-native performance and rich user experiences. As these applications grow in essential complexity, they also grow in accidental complexity due to the imperative callback processing style found in most web applications. The asynchronous nature of most of these applications also further compounds the issues due to guarantees around message ordering, and a level of indirection required in callbacks handling events.
Max Ogden is presenting…
Max used to live here in Portland, and at some point defected to work on noble causes with Code for America. Since then he’s been an Oaktown Coder (Oakland, the other city near San Francisco).
Brock Whitten is presenting…
Mighty Messaging Patterns
Best know for having co-created PhoneGap, Brock went on to work at Joyent where he created the Public API for the beloved (and now sunset) No.de Platform. He’s now working on the Harp Platform where he’s worked with a team to have created a dead simple publishing platform that uses Dropbox as its deployment mechanism. Much has been learned, he’s read to share.
In this talk, I will start with a crash course on the basic messaging patterns push/pull, pub/sub, and request/reply and then show a real example of how we have combined these patterns to build a custom message broker that we have used to build a fully distributed and modular architecture for the Harp Platform. I will share details about what we have learned and common pitfalls to avoid when building a messaging system for your needs.
Basic outline for the talk:
- how messaging can be useful
- crash course on the basic message patterns
- how to get started with zeromq/axon
- common pitfalls when in production
- proven trade secrets we have learned
By the end of the talk, my hope is that everyone will have a new appreciation for what can be achieved with massaging and will know where to begin when attempting to integrate messaging into their next project. I feel this aspect of building modern web applications is often overlooked and viable techniques need to be shared and discussed.“
Are you signed up? BUY YOUR TICKET FOR NODE PDX HERE
Want to learn more? http://nodepdx.org/
Want to know the dates? http://nodepdx.org/
Want to know who else is speaking? Stay tuned here or go check out http://nodepdx.org/!
Have a last minute request, idea, comment or a speaking proposal? http://nodepdx.org/
(Cross-posted @ Composite Code)