Internal Architecture

Internally, PowerNodes uses a state-of-the-art multi-tiered application architecture, implemented around business objects. This multi-tiered architecture is built upon EntityBroker Object/Relational mapping middleware, which not only makes PowerNodes database independent (and thus able to operate against SQL Server as well as Oracle databases), but also handles the communication between the FrontDesk client-side editor application and the server components running on the web server only using port 80 http.

The functionality of the PowerNodes Content Management System is split up into various modules. Every module is responsible for a certain group of functions that form a coherent sub-system. Standard groups are, for example:

  • PowerNodes.Cms, which contains the core functionality of the content management system
  • PowerNodes.Mbr, which handles membership management, which keeps track of users, their group memberships or their passwords
  • PowerNodes.Not, the notification framework, which includes mass-mailing functionality as well as the framework to send out change notifications to end-users (for example when a password has changed)
  • PowerNodes.Shp, which includes the online shopping system

The majority of modules are dependant on the functionality of other modules, like the CMS module relying on the Mbr Module to handle all its user management and security tasks.

Application flexibility

Every module contains a FrontDesk counterpart that handles user interaction in FrontDesk (like PowerNodes.FrontDesk.Cms, handling the user interface in FrontDesk for the PowerNodes.Cms module). The FrontDesk application dynamically creates its user interface given the metadata information stored in the modules, allowing the user an interface to reconfigure itself based on the available modules.