Tag Archives: Full Stack

An Introduction To Full-Stack JavaScript

via An Introduction To Full-Stack JavaScript – Smashing Magazine.

In my experience, full-stack JavaScript hits all the marks. You’ve probably seen it around; perhaps you’ve considered its usefulness and even debated it with friends. But have you tried it yourself? In this post, I’ll give you an overview of why full-stack JavaScript might be right for you and how it works its magic.

Part 2: Unit Testing Full Stack – AngularJS Part 1 of 3

via Unit Testing Full Stack Part 2 – AngularJS Part 1 of 3 – Development Thoughts and Findings.

This is part 2 of my multi part guide for setting up and testing a full stack JavaScript application. Next up is AngularJS. I’ve broken this up into 3 separate parts, as this is a bit more complex for testing the front end, since we have both unit tests and end to end tests. The parts will be broken up as follows:

Million user webchat with Full Stack Flux, React, redis and PostgreSQL

via Million user webchat with Full Stack Flux, React, redis and PostgreSQL | Elie Rotenberg.

Sexy, right? Flux over the Wire allows us to leverage the goodness of Flux to share a single source of truth between multiple clients, and update them in real time. This makes building things like chats, comments systems, or even auto-updating articles, fairly easy. Declare your data dependencies at the component level. Not only will they auto-resolve, but they will also get auto-updated whenever the backend is updated! For free, as in free beer!

Well, not entirely free. This makes a nice 1000-user chat demo, but now each user requires an active network connection and a server-side representation of its stores subscription to remain on your website. Multiply this by your average concurrent number of users, and you might have a problem. The exact amount of users your single-process Node app may handle properly vastly depends on how you batch your updates and how chattery your app is, but in my experience, this number hardly exceeds several dozens of thousands concurrent users for your typical chatroom app. This is already quite nice compared to what you may achieve without using Flux over the Wire or batched mutations, but likely not enough if you run a moderately large website. In addition, unless you add a layer of persistence to your app, then if your server crashes, your data is screwed.

So we need to:

  • Embed the Source of Truth in a persistent storage that can be safely shared between multiple action producers/updates consumers,
  • Make every possible bottleneck scalable (more servers = more clients = more $$$)

Video: ReactJS Conf Round-up 2015

via React.js Conf Round-up 2015 | React.


The conference is over, but the conversation has just begun.

Mihai Parparita detailed his efforts to hack his way to a React.js Conf ticket; James Longblogged about his first encounter with React Native; Eric Florenzano talked about how he perceives the impact of Relay, GraphQL, and React Native on software development;Margaret Staples blogged about her experience of being on-campus at Facebook HQ; Jeff Barczewski tied his experience of attending the conference up with a bow in this blog post filled with photos, videos, and links; Kevin Old left us with his takeaways; Paul Wittmannfound React Native freshly on his radar; and finally, undeterred by not being able to attend the conference in person, Justin Ball summarized it from afar.

And, in case you missed a session, you can borrow Michael Chan’s drawings, Mihai Parparita’s summary, or Shaohua Zhou’s day 1 / day 2 notes.

Keynote #

Tom Occhino opened with a history of how React came to be, before announcing Facebook’s answer to a long-looming what-if question: what if we could use React to target something other than the DOM?

Tweaking in real time

Brenton Simpson showed us how eBay brings Bret Victor’s feedback loop to your favorite editor using Webpack, react-hot-loader, and Ambidex.

Abstract Syntax Trees

Gurdas Nijor showed us how we can leverage some conventions of React to perform source code transformations that unlock an inspirational set of use cases.

Relay and GraphQL

Daniel Schafer and Jing Chen showed us how Facebook approaches data fetching with React, giving us an early peek at the forthcoming duo of Relay and GraphQL.


James Long explores what might happen if we introduce channels, a new style of coordinating actions, to React.

React Router

Michael Jackson reminded us that URLs should be part of our design process, and showed us how react-router can help to manage the transitions between them.

Full-stack Flux

Pete Hunt showed us how a Flux approach can help us scale actions and questions on the backend in addition to the frontend.


Jason Bonta showed us how complex user interfaces can get, and how his team keeps them performant as they scale. He also had the pleasure of open-sourcing his team’s work on FixedDataTable.

FormatJS and react-intl

Eric Ferraiuolo showed how you can bring your app to a worldwide audience using a series of polyfills and emerging ECMAScript APIs.


Ryan Florence showed us how easy it is to transition from a career selling life insurance, to a burgeoning one as a software developer. All you have to do is to learn how to say “yes.”

React Native

Christopher Chedeau showed us how to bring the developer experience of working with React on the web to native app development, using React Native.


Andrew Rota explained how React and Web Components can work together, and how to avoid some common pitfalls.


Lee Byron led a master-class on persistent immutable data structures, showing us the world of possibility that they can unlock for your software, and perhaps Javascript in general.

Beyond the DOM

Jafar Husain told us a story about how Netflix was able to push React into places where the DOM could not go.

Data Visualization

Zach Nation showed us how we can produce visualizations from over 45 million data points without breaking a sweat.

React Refracted

David Nolen gave us a view of React from a non-JavaScript perspective, challenging some common intuition along the way.

Flux Panel

Bill Fisher coordinated a Flux panel together with Michael Ridgway, Spike Brehm, Andres Suarez, Jing Chen, Ian Obermiller, and Kyle Davis.

Component communication#

Bonnie Eisenman led us through the ‘adapter’ approach to inter-component communication taken by her team at Codecademy.

Flow and TypeScript

James Brantly demonstrated how we can reap the benefits of static typing using both Flow and TypeScript.

Core Team Q&A

Tom Occhino, Ben Alpert, Lee Byron,Christopher Chedeau, Sebastian Markbåge, Jing Chen, and Dan Schaferclosed the conference with a Q&A session.

Video: Full Stack Flux

Pete Hunt actually doesn’t talk about the future of JavaScript layout systems. Instead, this talk is all about full-stack Flux.