Managing large application architecture

Página 1

How much of this architecture is instantly re-usable?

Can single modules exist on their own independently?

Could I easily take one of your modules, drop it into a page and it would start working?

How much do modules depend on other modules in the system?

If specific parts of your application fail, can it still function?

How easily can you test individual modules?

Five traits of well managed Javascript: http://www.ifwe.co/blog/posts/five-traits-of-well-managed-javascript/

Dependencies are *always* declared

3rd party code is shimmed

Definitions are separate from executions

Dependency loading is async

Modules do not depend on globals

Excellent list of resources at: http://superherojs.com/

See: https://gist.github.com/desandro/4686136 for good analysis on the benefits of require.js

Great article from Addy Osmani: http://addyosmani.com/largescalejavascript/

"The secret to building large apps is never build large apps. Break your applications into small pieces. Then, assemble those testable, bite-sized pieces into your big application" -

Justin Meyer, author JavaScriptMVC

"The key is to acknowledge from the start that you have no idea how this will grow. When you accept that you don't know everything, you begin to design the system defensively. You identify the key areas that may change, which often is very easy when you put a little bit of time into it. For instance, you should expect that any part of the app that communicates with another system will likely change, so you need to abstract that away." -

Nicholas Zakas, author 'High-performance JavaScript websites'

"The more tied components are to each other, the less reusable they will be, and the more difficult it becomes to make changes to one without accidentally affecting another" -

Rebecca Murphey, author of jQuery Fundamentals.

What is REST: REST stands for Representational State Transfer

New Page