Developers creating JavaScript applications these days usually use a combination of MVC, modules, widgets and plugins for their architecture. They also use a DOM manipulation library like jQuery.
Whilst this works great for apps that are built at a smaller-scale, what happens when your project really starts to grow?
In this talk, I go through a number of topics including:
- MVC on the client-side and organizing your application
- Frameworks you can use to implement this pattern (and others)
- Effective (decoupling) design patterns for large-scale JavaScript (and jQuery) application architecture that have previously been used at both AOL and Yahoo amongst others.
You'll learn how to keep your application logic truly decoupled, build modules that can exist on their own or be dropped into other projects and future-proof your code in case you need to switch to a different DOM library in the future.
View the slides for this talk on SpeakerDeck (128 slides)
* This talk was last presented at the 2011 jQuery Summit.
Related Resources
- TodoMVC - a common list application implemented in a dozen JavaScript MVC frameworks
- Backbone-aura – Integrating Backbone.js with AMD modules, RequireJS and the mediator and facade patterns
- Writing Modular JavaScript – my guide to using recent module formats like AMD and CommonJS
- Patterns For Large-Scale JavaScript Development – an expansion on some of the ideas discussed in this talk
I just really dig JavaScript. I'm a writer, speaker and a JavaScript developer for AOL (yes, we're still around!).
Pingback: Large-scale JavaScript Application Architecture | EtondeGroup Blog of Web Applications
Hi,
I really appreciate your work here.
As a self made developer with half degree i'm not use to follow the book and sometime i get shocked when i see formal explanation for some implementation i done.
Regarding async module, i just made some alfa framework, as you did, that completly fit into your description.
The main application offer module registering, module lifecycle, allow publisher/ subscriber so it also mediates.
The ajax layer is pipelined so the mediator could abort ajax requeste before or after execution.
Well, im really glad and i congratulate you for this valuable contribution.
I will try to keep in touch with your site.
Great work Addy on the presentation and associated Technical Report on your site. Have checked out your backbone-aura Github project and think your demo app could be less coupled and use internal Backbone.Events as a Mediator instead. My approach is here: https://github.com/radekstepan/fundamental.js
Would love to hear your comments.
Hi Addy!
Your work fits really well into what I'm trying to archieve for the company I am working with.
Where do you give the talks on those topics? Are there any videos as well? I really would like to hear a talk from you and describe you my experiences in synchronizing the work of multiple different teams in one united front end experience.
sincerely
Benedikt
@Benedikt
I usually give talks on these topics in London, where I'm based, but you can also find videos about them on the Environment for Humans site from the last jQuery summit. I believe they're currently for sale (I don't profit from these), but as soon as a free version is available I'll post it up on the site. Feel free to let me know if you have any other questions at all.