Technology - Scala, Play, Akka, Spray

Timing is everything. If a system does not respond in a timely manner then: at best, its value is greatly diminished; and at worst, it is effectively unavailable. Reactive systems need to meet predictable response time guarantees regardless of load or datasets size, even in the presence of burst traffic and partial failure conditions.

In this talk we will explore what is means to be responsive and the fundamental design patterns required to meet predictable response time guarantees. Queueing theory, Little's Law, Amdahl's Law, Universal Scalability Law - we'll cover the good bits. Then we'll explore algorithms that work with these laws to deliver timely responses from our applications no matter what gets thrown at them.


Martin Thompson - High-performance and low-latency specialist

Martin is a high-performance and low-latency specialist, with experience gained over two decades working on the bleeding edge of large transactional and big-data systems. He believes in Mechanical Sympathy, i.e. applying an understanding of the hardware to the creation of software as being fundamental to delivering elegant high-performance solutions. The Disruptor framework is just one example of what his mechanical sympathy has created.

Martin was the co-founder and CTO of LMAX. He blogs at mechanical-sympathy.blogspot.com, and can be found giving training courses on performance and concurrency when he is not cutting code to make systems better.



React London 2014: Responsive Trait - Responding in a Timely Manner - Martin Thompson

Jonas Boner asked me to write an abstract for this talk. We were talking about some of the things I'd learned while building resilient systems. I mentioned a few simple things I knew - he said "Tell them these things, stories from real-life experience are always fun"

I sat on the underground, with my notepad out and started scribbling. The planned title of the talk was 7 things I'd learned about programming. But by the time I got to Kista I had a list of 32 things.

By the time I've written the talk it might be more than 32.

So I'll talk about the K things that I've learned where K >= 32

About the speaker


This person is speaking at this event.

Joe Armstrong - Principal Inventor of Erlang

Joe Armstrong is one of the inventors of Erlang.

When at the Ericsson computer science lab in 1986, he was part of the team who designed and implemented the first version of Erlang. He has written several Erlang books including Programming Erlang Software for a Concurrent World. Joe held the first ever Erlang course and has taught Erlang to hundreds of programmers and held many lectures and keynotes describing the technology.

Joe has a PhD in computer science from the Royal Institute of Technology in Stockholm, Sweden and is an expert in the construction of fault tolerant systems. Joe was the chief software architect of the project which produced the Erlang OTP system.

He has worked as an entrepreneur in one of the first Erlang startups (Bluetail) and has worked for 30 years in industry and research.


React London 2014: Resilient Trait - Joe Armstrong

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.

Technology - Scala, Play, Akka, Spray

alboko