DeveloperWeek 2015 Conference + EXPO

Every engineering team has processes, whether they're in someone's head or documented for all to read. But for a company and its engineering team to sustain its culture as it grows, even more important than what those processes are or how they're recorded is how they undergo change. At New Relic, we have a culture of openness that we intend to keep, so we've been experimenting with using GitHub Pull Requests to change our "laws of engineering". We've learned a lot so far. Come see why we did it and what you can learn from our experience.

It's undeniable that WebRTC is disrupting the VoIP industry and redefining what communicating means. Enabling secure real-time communications applications in the browser without requiring any plugin or fancy equipment on the client side, WebRTC has the potential to become the next standard of communications.

So where does that leave SIP? Could it be replaced by WebRTC? Clearly, the two overlap in their function. However, to understand the issue, we need to consider other important parts of the communication process like signaling or being able to connect a wide range of devices (not just smartphones and laptops).

There is a lot of buzz about WebRTC, and there already nearly 100+ different open-source projects, API’s, and WebRTC tool-kids out there. Where do you begin? And when you begin, how do you make sure you develop WebRTC in a way that will last? In this session we will take a look at: 

1. What to look for in a WebRTC API
2. Adding WebRTC to your first app
3. Considerations for scaling WebRTC
4. Dealing (and not dealing with) with WebRTC media

Concurrency control is one of the main aspects of multi-player games where all the checks, conditional writes and game state updates must be made as fast as possible and with minimal client/server calls in order to keep the game fair and square. This is especially critical in turn-based games where careless implementation (such as putting code that alters the game state in the client) can lead to concurrency related “race condition” from creeping in. 

As developers move to create applications that engage in real-time interactions, they are increasingly adopting open source technology stacks that include Node.js, Javascript MVC frameworks such as AngularJS, asynchronous messaging via Socket.io, and NoSQL databases such as the open source Aerospike DB.

The session will begin with a brief introduction to the open source Aerospike DB. Then, it will specifically address how to gain concurrency control in a multi-user application using User Defined Functions. 

To illustrate, we will look at a web-based multi-player game written in Node.js that uses Aerospike Node.js Client. Other technologies used: AngularJS, Socket.io and Lua