Front-End Software Design Goals
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).
Final ThoughtsBuilding 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 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.