HTML5 Application Architecture

Layers

You can do everything in HTML5, and for small single purpose apps it can make sense.

For larger HTML5 applications there are usually three core layers:

• HTML5 UI
• Server or Application container, depending on context
• Database backend

There seems like there's no end to the number of frameworks emerging to compete as the HTML5 MVC layer. I haven't used too many; Sencha seems to making some inroads, but I wasn't happy using it. I've used Palm Mojo and Enyo for applications, which I really enjoyed working with, which is why I'm pursuing Enyo MVC for now.

I can't say I'm sold on JavaScript in general, partly because functional programming is relatively new to me, but mostly, because JavaScript. But switching mind sets between a Java server and JavaScript front end can be pretty annoying, if not exasperating at times.

Set up Link-to-next

Return Home