Our Facade Is Ready Too!

picture-11

This is the image I wanted to appear whenever a user got a 500 error message. The team didn't like it, though :( . Oh well. A different one will be used. Hopefully, you will never get to see it.

The Merrcury Engine (the software behind LetMeGo) is composed of several subsystems (see details). Three of these subsystems are known as the “communication subsystems”. They are in charge of all of the interactions we have with our customers. I recently blogged about the completion of the Morrison subsystem (email interactions) and the Cockerr subsystem (human interaction via tickets). Today, we are happy because the Web subsystem (the only one without a funny name) has reached beta stage, too. :)

The Web subsystem is in charge of allowing our users to interact with our business via the web (obviously). Needless to say, this is how our customers will interact with us most of the time. The Web subsystem does not include any business logic (almost). However, it sits in the middle, between the user and the subsystems that handle the business logic.

The Web subsystem of Merrcury includes many neat features. Some of them are the following:

  • A lot of AJAX, courtesy of jQuery, mostly.
  • Whenever users see a date and time in our site, it will be render using the time zone of the computer.
  • ACL-based permissions, courtesy of CakePHP.
  • Friendly forms.
  • Automatic browser check that displays alerts whenever the browser being used hasn’t been tested with the site.
  • Every time a signed-in user gets a 500 error message, a ticket will be opened automatically, so that we can personally apologize for the issue.
  • As with the Cockerr and Morrison subsystems, the Web subsystem is capable of full internationalization.
  • And much more!

Pretty much every member of the team helped in the coding and QA of the Web subsystem (with the exception of myself, your dear author of these fine blog posts.) Thank you guys!

Alexander Torrenegra

P.S. Here is the current status of all the subsystems and scopes required for our full beta release:

Scope Progress
Scope Status
Web Subsystem Ready for Beta! :)
Morrison Subsystem Ready for Beta! :)
Cockerr Subsystem Ready for Beta! :)
Hendrrix Scope Ready for Beta! :)
Sinatrra Scope 15% of QA for Beta
Arrmstrong Scope 80% of Coding for Beta
Rrose Scope Ready for Beta! :)
Charrly Scope 15% of Coding for Beta
Mozarrt Scope Alpha Ready
Mastrropiero Scope 25% of Coding for Beta
Kubrrick Scope 45% of Coding for Beta
Brrown Scope 15% of Coding for Beta
Marrley Scope 100% of UI Design
Waterrs Scope 5% of Coding for Beta

About the Author

Alexander is LetMeGo's co-founder and jefe. Here is his LetMeGo profile. You can follow him on Twitter @torrenegra.

No Comments

Start the ball rolling by posting a comment on this article!

Leave a Reply




XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <embed> <i> <object> <p> <q cite=""> <script> <strike> <strong>