Building a Better Web
June 11–12, 2018: Training
June 12–14, 2018: Tutorials & Conference
San Jose, CA

Reactive programming for frontend developers

1:30pm–5:00pm Tuesday, June 12, 2018
Frameworks and Libraries
Location: 210 D/H Level: Beginner
Secondary topics:  Hands-on, Technical

Who is this presentation for?

senior developers, tech leads, lead developers

Prerequisite knowledge

Javascript ES6, experience with building web applications/sites. Nice to know a bit of functional programming but not essential

Materials or downloads needed in advance

Github repository Slides in PDF Webpack Babel Favourite editor/IDE

What you'll learn

the attendees will learn how the reactive paradigm works and they will compare in practice 2 implementations that will allow them to put in practice immediately in their projects


This is a workshop for frontend developers that want to move into the Reactive paradigm using real applications that are evolving over time.
During the session, we will analyse the benefits of the reactive and functional paradigms, in particular, we are going to build the following examples:
. analysing a simple stock application with Vue.js
. build a similar application but with VueX
. analysing a simple maps application with MobX
. building a similar application but with MobX State Tree

All the applications will cover the following key parts of a frontend application like:
. consuming remote endpoints
. structuring an application (view, stores, actions…)
. handling the application state in a reactive way
. unidirectional data flow

Photo of Luca Mezzalira

Luca Mezzalira


System Architect at DAZN, Google Developer Expert on Web Technologies, London Javascript Community Manager and author of the book “Front-End Reactive Architectures”

Leave a Comment or Question

Help us make this conference the best it can be for you. Have questions you'd like this speaker to address? Suggestions for issues that deserve extra attention? Feedback that you'd like to share with the speaker and other attendees?

Join the conversation here (requires login)