Modern web applications follow most performance guidelines from Yahoo! Exceptional Performance but in this blog post, I'll explain some of the software engineering design goals of Mojo's dependency management for asynchronous UI controllers in achieving performance, maintainability, and ease of use. In addition to this, I'd like to highlight that there are many libraries that are CommonJS AMD compliant, such as, Dojo's Backdraft Loader, RequireJS, and Curl.js -- Mojo's dependency management is inspired by these libraries but I specifically wrote Mojo's Mapper to make it easier for platforms it specific to its domain.
In the above example, we can find ourselves easily mapping HTML elements that are present in the current state of the DOM to Controllers using JavaScript:
In this case, if one of the software engineers or product managers were to disable the Registration feature on the platform, Mojo's Mapper will detect the DOM change (notice that Registration isn't there) and will not try to inject Registration Controller. This is easier for any platform as we can ensure there won't be any JavaScript errors being thrown at a user.
Commonly, we try to take a proactive layering approach to rolling out features to customers -- sometimes deploying 10-20 times per day. This means, automated tests on the UI and the backend, as well as, Mojo's approach to only execute JavaScript (within a controller) when a particular feature is enabled.
Good luck and have fun,
Jaime Bueza
Jaime Bueza is a software engineer in Vancouver, British Columbia, Canada. He has developed web applications for Nintendo, Starbucks, Bacardi, Nike, Electronic Arts, Ritchie Brothers, Kiwi Collections, Cox Communications and Microsoft. When he's not developing useful software that constantly evolves with business requirements, he's writing open source software and helping developers in the Windows Azure NodeJS community.
Primary Design Goals for Front-End Microframework (Mojo)
- Should be backend-end agnostic
- Should understand DOM fractures / feature gating
- On the platforms I work on, we have the capability to enable/disable certain features in real-time or even rollout features to a specific subset of users at any point in time without requiring additional deployments. Inspired by James Golick's Rollout library.
- Should understand when a specific dependency isn't in the DOM and automatically fetch it by resource name
- Should understand where dependencies are (CDN, Blob Storage, Relative)
- Should enforce implementation silos to reduce "too many cooks in teh kitchen" situations on distributed teams
- Should enforce message passing as a way of communicating between controllers instead of directly invoking commands (remember: controllers are asynchronously loaded).
In this case, if one of the software engineers or product managers were to disable the Registration feature on the platform, Mojo's Mapper will detect the DOM change (notice that Registration isn't there) and will not try to inject Registration Controller. This is easier for any platform as we can ensure there won't be any JavaScript errors being thrown at a user.
Commonly, we try to take a proactive layering approach to rolling out features to customers -- sometimes deploying 10-20 times per day. This means, automated tests on the UI and the backend, as well as, Mojo's approach to only execute JavaScript (within a controller) when a particular feature is enabled.
Final Thoughts
Building a front-end that bakes in publish/subscribe, implementation silos, dependency management is just as important as writing web services that scale effectively on the Cloud. On any platform, an intelligently engineered front-end that can synergize with your platform's performance initiatives and feature gating mechanisms -- making it even more valuable as you deploy features continuously to your customers.Good luck and have fun,
Jaime Bueza
Jaime Bueza is a software engineer in Vancouver, British Columbia, Canada. He has developed web applications for Nintendo, Starbucks, Bacardi, Nike, Electronic Arts, Ritchie Brothers, Kiwi Collections, Cox Communications and Microsoft. When he's not developing useful software that constantly evolves with business requirements, he's writing open source software and helping developers in the Windows Azure NodeJS community.
Comments