What does it take to build a complex single page application (SPA)? How do you model state in a way that can be reasoned with yet scales with functionality and remains maintainable? How do you separate your view code from your state and update state in a deterministic manor? We'll answer these questions using a real world open source sample application, Reactive Trader, build on React and Evented State Processor (esp-js). Keith Woods has been working in the city for several years on real time push based FX trading platforms. Consulting at various banks he has helped developed some of the worlds leading FX platforms using a range of differing technologies (including .Net, Java and JS). He works right across the stack. He is the author of ESP (esp-js, esp-net), build to solve complex state modelling problems.
I'd like to share two stories about bugs encountered during the day-to-day use of NodeJS. The first story is about a bug that plagued 3x developers in the office, the second story is about a major bug in production. These bugs are fat juicy and obscure, relating to non-obvious behaviour in the NodeJS core. I'll be presenting both stories as a timeline of their discovery through mitigation, understanding and resolution.
In this talk I'd like to show a quick example on how to create an isomorphic application with Hapi.js and React, in particular focusing why Hapi.js allows to create configurable and well organised code and how to use React as views for your isomorphic application. Speaker: Luca Mezzalira Linkedin: https://uk.linkedin.com/in/lucamezzalira **Twitter**: https://twitter.com/lucamezzalira