I'll explain the Reactive Manifesto from a perspective of a practitioner. Starting from "when to adopt it" to how to understand its four points. Through this lens I want to change the way you look at web applications.
YOU MAY ALSO LIKE:
Reactive Manifesto - what's this and when/why should I care?
Marek is a software engineer who is extremely completion-oriented. He believes passionately in the future of technology based solutions and often can be found tinkering with leading and bleeding edge ideas. Starting from LAMP, going through Nodejs, Grails to Scala. Currently in a role of CTO at Evojam - software solution provider focused on building scalable, premium-quality web apps. Previously CTO of San Francisco based startup 1-Page which IPOed last year on Australian Stock Exchange.