Rob Harrop
From Skipjaq
CTO @ Skipjaq. We optimise your applications using fancy machine learning cleverness.
In a past life, I was co-founder of SpringSource which was acquired by VMware. At SpringSource I was a major contributor to the Spring Framework and published the best-seller Pro Spring.
After SpringSource I spent some time working in consumer finance as co-founder and CTO of Bamboo Loans.
Blog: http://www.skipjaq.com
Java, JVM, Java SE/EE
Going Reactive
Reactive architectures are becoming ever more popular in the Java world as developers come to understand the benefits to code comprehension, de-coupling and testability.
Work is already underway to standardise a set of Reactive Stream APIs and in Java 9, we'll see Reactive as a core part of the JDK with the Flow API. Now is the time to learn how to get the most from the Reactive model.
In this talk, attendees will learn both the why and the how of Reactive Java. We'll start with a brief history of Reactive to understand what problems it solves, and why we might want to fit it into our applications. The majority of the session focusses on how to use Reactive Java and attendees will learn how to:
- Identify and use the common Reactive patterns
- De-couple parts of their applications using Reactive components
- Improve testability of their components using Reactive
- Use Reactive as a model for asynchronous processing in a real application
Architecture, Performance and Security
Understanding Microservice performance
The world at large seems sold on microservices as a way to build large, quality systems at the speed needed to compete in today's market. However, microservices are not without their downsides, one of which is the difficulty of reasoning about and optimising the performance of mircoservices working in tandem.
In this session, attendees will learn the key concepts needed to measure the performance of their services, identify potential bottlenecks and take corrective action to ensure services perform as needed.
Before we can reason about the performance of connected services, we must understand how to reason about services in isolation. The first half of the session is dedicated to discussing how to measure service performance correctly, what metrics matter and how to compare the performance of a service over time.
In the second half of the session, we take our single-service knowledge and expand it out to reason about a set of services working together to provide some aggregate function. We'll see how the performance of each service affects the performance of the whole, and learn how to identify where to focus our optimisation efforts.