Skip to main content

Front-End Software Design Goals

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.

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).

Mojo Mapping HTML Elements to Controllers
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.

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.
Post a Comment

Popular posts from this blog

TextMate Tutorial: How to add a Strikethrough keybind to your Markdown bundle

Markdown is awesome for quickly generating Readme's on Github. After looking at other projects using the strike tag, I've decided to create a custom keybind for it in my TextMate Markdown bundle. Here's how:

1) Click the + sign on the bottom left and click New Command.
2) Paste this into the editbox and make sure you name your command "Strikethrough".

For the input field, select WORD in the drop down.
For the output field, select "insert as snippet".
As for the keybind, you can totally map it to whatever you're comfortable with but I chose Command-D as it is the same thing in Microsoft Word.


Using Git Hooks: Prepare Commit Message to automatically prepend branch names on commit messages

When you're practicing branch by feature with distributed version control, typically you'll get assigned a ticket or issue and that ends up being your feature branch. Instead of always typing in the branch name in every commit, you can edit your Git hooks (specifically prepare-commit-msg).

Assuming that this is a brand new git repository:

mv .git/hooks/prepare-commit-msg.sample .git/hooks/prepare-commit-msg
vi .git/hooks/prepare-commit-msg

Edit the file by commenting out what was originally in the file and then add this:

Now, whenever you make a commit, it should show up like this in the log:

Since GitHub and Bitbucket both support Emojis inside commit messages, you can do something cute like this

Want more emojis? check out the Emoji Mardown Cheatsheet!

NodeJS Hack Session: MMO Pokemon with NodeJS/WebSockets

The primary focus of this proof of concept is to determine how easy it is to build real-time web applications for all iPad, iPhone, droids, Safari, Chrome users on top of NodeJS (non-blocking event driven server side Javascript platform). The proof of concept was built within 6-8 hours including the following:

Uses Express framework for server side Javascript development (inspired by Rails / Sinatra / Django)Uses EJS for templating language (much like Django templates and symfony) -- allows partials and passing parameters into partials like symfony PHPReal-time chat using WebSocketsArena Queueing System for real-time competitive matchplay using WebSocketsHTML5 AudioCSS3 transitions for all hand cards, tappable cards, transparent panels, rounded corners, drop shadowsFallbacks for Firefox, IEFirefox/IE will fall back to Flash socketIE will fall back to XHR long poll if the user doesn't have Flash installedNoSQL CouchDB for fetching users and soon cards, achievements, friend associat…