Robust JavaScript Application Architecture

In October, 2014, I was coerced invited to deliver a talk at the first FullStack conference in London, a conference focused on Node.js, JavaScript and hackable electronics. The conference was an interesting cross-section of all things related to JavaScript.

A topic that’s been on my mind lately is how to choose a robust architecture that’s right for your application. The point of the talk was to encourage people to challenge assumptions and not just choose whatever is popular or whatever they know best. I’m sure some attendees in the audience just wanted to be told which framework to use, but the point was to make people really challenge themselves, and find solutions that work now, but are flexible enough to change later.

The talk is now available online:

JavaScript architecture assistance

JavaScript Application architecture is something we specialize in at SitePen, as we see far too many organizations struggling in this area. If you need assistance, please contact us to talk more about your application and how we can help.

Comments

ca0v

This talk was about the importance of modularity. Your audience was already AMD/CommonJS aware, but the AMD approach to development is genius and a huge contribution/boon to modular design and testing. I’m excited for the productivity gains Typescript + Dojo 2.0 will bring. Did you hint that a future dijit library might target multiple platforms?