GOTO is a vendor independent international software development conference with more that 90 top speaker and 1300 attendees. The conference cover topics such as .Net, Java, Open Source, Agile, Architecture and Design, Web, Cloud, New Languages and Processes

Todd Montgomery, Network, Systems, and DevOps Geek

Todd Montgomery

Biography: Todd Montgomery

Todd is a networking geek who has researched, designed, and built numerous protocols, messaging-oriented middleware systems, and real-time data systems, done research for NASA, and has contributed to the IETF and IEEE. Todd currently works for Informatica and is responsible for architecture of Ultra Messaging

Presentation: Java vs. C/C++ Panel

Time: Wednesday 12:10 - 13:00 / Location: French

This is a question that almost everyone doing a major project asks: should I use C++, or Erlang, or Java, or C#? Maybe it is more abstract than that, such as, should I use native code, like C++, or a managed runtime, like Java? Mostly, this is a matter of taste. Or is it? When it comes to ultimate performance, most applications are native, C++/C, with even having some hand crafted assembler mixed in. But can Java, or any managed runtime in general, do nearly as good? Or maybe it could do better than native code. What could applications do to leverage the most out of these languages? With C++11, has the game changed? With Java 7 or 8, has the game changed? Or has the game really changed with the acceptance of Erlang? These and more, fellow developers, will be questions asked on this panel. It is native code vs. managed runtime in the game of performance!
Panel: Gil Tene, Martin Thompson, Tom Rodgers, Artur Laksberg
Moderator: Todd Montgomery

Presentation: Building High Performance Protocols

Time: Wednesday 16:30 - 17:20 / Location: French

Like any good piece of software, a performant network protocol implementation is a marriage of careful design of both protocol and code. In this session, we will let the cat out of the bag on several tips and tricks that have been employed over many years to design and implement network protocols that are high performance and designed for backwards compatibility. We will also explore what NOT to do, as well as, what to include in a protocol and what belongs higher up. So many lessons have been learned going from IPv4 to IPv6 and from HTTP/1.1 to SPDY. These great ideas apply well beyond network protocols and they have been the sole domain of network geeks for far too long.