Presentation: TweetReactive Programming Models for IoT

The predicted explosive growth of the Internet of Things presents complex problems for the Java developer in both infrastructure demands and user experience. The Reactive Manifesto (www.reactivemanifesto.org) and Reactive Programming paradigms such as micro-services and reactive extensions/streams hold tremendous promise as a means to rapidly evolve these systems with scalability and resiliency as primary attributes. In this session, we shall: (1) explore a hands on approach to bringing these concepts to a handful of IoT use cases, (2) introduce a new project called Katalyst geared at making IoT-scale problems tractable and letting developers get back to making cool concepts a reality, and (3) show how easy it truly can be to develop solutions that scale, evolve, and seamlessly communicate.

Presentation: TweetWhat is a Reactive Application Part I

Reactive is becoming the new cool kid on the block when it comes to developing mission critical applications. What is the big deal? The old hands that were involved in the likes of Erlang and Tandem will say this is nothing new. Indeed that is very true. However many seem to have lost their way with enterprise applications and descended into the tar pit of big frameworks such as JEE, or built Rails apps that fall apart when they grow up into successful applications. Yet some large scale web companies, telco providers, financial trading firms, and multi-player online games are delivering services that are always available by being resilient to failures, always responsive so that users are not left waiting, and reactive to load by elastic use of resources. How do they offer this level of service? Well that is what we want to discuss.

In this deep dive we will explore what are considered the desirable characteristics of reactive applications via a series of lightening talks. Then we will discuss the design approaches that can be taken to achieve these desirable characteristics. The discussion will be open to the audience so everyone can explore this topic and learn.

Presentation: TweetWhat is a Reactive Application Part II

Reactive is becoming the new cool kid on the block when it comes to developing mission critical applications. What is the big deal? The old hands that were involved in the likes of Erlang and Tandem will say this is nothing new. Indeed that is very true. However many seem to have lost their way with enterprise applications and descended into the tar pit of big frameworks such as JEE, or built Rails apps that fall apart when they grow up into successful applications. Yet some large scale web companies, telco providers, financial trading firms, and multi-player online games are delivering services that are always available by being resilient to failures, always responsive so that users are not left waiting, and reactive to load by elastic use of resources. How do they offer this level of service? Well that is what we want to discuss.

In this deep dive we will explore what are considered the desirable characteristics of reactive applications via a series of lightening talks. Then we will discuss the design approaches that can be taken to achieve these desirable characteristics. The discussion will be open to the audience so everyone can explore this topic and learn.

Presentation: TweetReactive Programming Models for Internet of Things

The predicted explosive growth of the Internet of Things presents complex problems for the Java developer in both infrastructure demands and user experience. The Reactive Manifesto (www.reactivemanifesto.org) and Reactive Programming paradigms such as micro-services and reactive extensions/streams hold tremendous promise as a means to rapidly evolve these systems with scalability and resiliency as primary attributes. In this session, we shall: (1) explore a hands on approach to bringing these concepts to a handful of IoT use cases, (2) introduce a new project called Katalyst geared at making IoT-scale problems tractable and letting developers get back to making cool concepts a reality, and (3) show how easy it truly can be to develop solutions that scale, evolve, and seamlessly communicate.