Reactive Streams with Spring Reactor-Core

Are you going?

10 people going


Needs a location


We'll have two 45 minute presentations for this meeting.

-------- PRESENTATION 1 --------
Imagine the rains in Portland (difficult, but do try). Clouds produce the rain, the storm-drain drains it. This is a good analogy for what reactive-streams has to offer. Cloud is the Producer of the stream of rain drops
Storm Drains are the Subscriber.

To take the analogy further - the raindrops can be produced by multiple clouds, hence the production can be asynchronous and similarly there will be a lot of different storm drains, thus the draining can be asynchronous. Reactive streams are designed to work with such kinds of asynchronous producers and consumers.

An interesting thought is what happens if the storm drains cannot drain faster than it rains - it floods. What if we could prevent it - this is where a concept called back-pressure comes in, what if the storm drains could send a signal to the cloud about the rate that they are comfortable consuming the raindrops at!

If this intrigues you, we will dig deep into the Reactive Streams specification( and how Spring Reactor-core project( makes it simple to produce and consume streams of data.

Biju Kunjummen is a Lead Software Engineer at Nike and works on Nike’s homegrown CMS product (Content Management System) which powers the content of, Nike App and other Nike experiences. He has worked in the software industry for 20 years and loves to share his learnings. He blogs at

-------- PRESENTATION 2 --------
Even in cloud environments, a lot of engineering teams still spend plenty of time thinking about infrastructure (VMs, load balancers, auto-scaling groups, etc...). Let's talk about Platform as a Service and the trade offs. This talk focuses on how to quickly get Java workloads running in Azure and how to scale them. We'll include a demo that showcases PaaS workflow integration into common Java tool chains.

Tyler Holmes is a CTO and Practice Lead for Axian, a local software and data engineering firm. He's been working in various stacks doing consulting/professional services for 15+ years.
Tyler Holmes: