ZZ is a platform for web services and service based websites that require solid support for rich user interfaces in a fail-safe and scalable architecture.
The happy days of complete backend supremacy are gone for good. Since the introduction of AJAX – the asynchronous 'invisible' request/response – web users have gotten used to fast responsiveness and immediate interaction.
No backend can by itself deliver the required tools for such a user environment, and adding the frontend as an afterthought simply doesn't make sense any more.
And the extensive use of AJAX introduces a range of new security problems – challenges that cannot be well attended from a backend point of view alone.
Thus the current-day web arena calls for an integrative view on the frontend-backend dichotomy – ZZ is, among other things, an attempt to target these issues.
• deliberate frontend-backend integration
• safety and security
• high performance, low overhead
• thorough error handling
• manageable and reusable code
• systematic codebase and documentation
Being a completely modular system, ZZ doesn't really care if everything – user and application databases, dynamic content generation, static content delivery – is squeezed into a single server, or placed on a range of different servers.
It's only a matter of configuration.
Several people have asked if ZZ is a content management system. Nope, it's not.
ZZ will probably at a later time offer some kind of CMS module, but the main purpose is not to deliver just another text cataloguing machine (or any other particular functionality, for that matter).
The idea is to provide a safe and comfy container for (almost) whatever kind of web application one could think of.
This site is not based on ZZ, and it's situated on a choked virtual server.
So please don't evaluate ZZ's performance on the basis of this site.