Topic: How To Transform Java Shops Into Reactive Shops
The term Reactive has certainly become much more popular recently. It seems that today everyone is going Reactive in one way or another. While the level of interest in things Reactive is high, the reality is that many of us are in the midst of internalizing what it means to be Reactive. What are the architectural features of Reactive Systems? How do I write Reactive code? Do I have to un-learn what I know and develop entirely new skill sets?
These are some of the questions we will explore in this session. We will start with the fundamental core concepts of Reactive Systems and Reactive Programming. We will also discuss how you can gauge how Reactive you are as a developer or architect and how Reactive are your current or planned application systems. We will also look into some of the directions of what is happening in the Reactive Systems space. While the discussion will be somewhat from a Java Team perspective the topics covered should be relevant to anyone interested in Reactive Systems development.
Speaker: Hugh McKee is a developer advocate at Lightbend.
He has had a long career building applications that evolved slowly, that inefficiently utilized their infrastructure, and that were brittle and prone to failure. That all changed when we started building reactive, asynchronous, actor-based systems. This radically new way of building applications rocked his world. As an added benefit, building application systems became way more fun than it had ever been. Now he is focused on helping others to discover the significant advantages and joys of building responsive, resilient, elastic, message-driven applications