The world operates in real time. Anything else is an illusion. Events happen all around us, that is why they are "events”. The days when we can look at synchronous method calls as the only interaction model have been dead for a while. We just never wanted to fully admit it. Well, it’s beyond time to embrace asynchrony. We’ve been doing it all along anyway with protocols and networking! Let’s (re)learn all the lessons from those guys! How did protocols evolve from request/reply, such as HTTP, to more asynchronous protocols, such as WebSocket? What are best practices (and things to avoid) for making applications asynchronous and event driven? How do architectures change when asynchrony is the new normal? What is this loose coupling and why is it good?

About the speaker

Todd L. Montgomery - Chief Architect for Kaazing

Todd is a networking hacker who has researched, designed, and built numerous protocols, messaging-oriented middleware systems, and real-time data systems, done research for NASA, contributed to the IETF and IEEE, and co-founded two startups.

He currently works for Kaazing as Chief Architect.