DownloadOpen Enterprise is a very ambitious project that comprise some full opensource components to provide a strong alternative to the existing commercial software.
Open Enterprise is cross-platform: Windows / MacOSX / Linux / BSD / Solaris / Unix.
License
GNU General Public License version 2.0 (GPLv2)Follow Open Enterprise
Other Useful Business Software
Cloud SQL manages your databases so you don't have to, so your business can run without disruption. It automates all your backups, replication, patches, encryption, and storage capacity increases to give your applications the reliability, scalability, and security they need.
Rate This Project
Login To Rate This Project
User Reviews
-
OpenFramework is a PHP/Javascript framework like ZendFramework or CodeIgniter or other similar frameworks. All PHP / Javascript code is Object-Oriented. The code is clean and is written with nTier architecture in mind (distributed architecture). The JQuery / JQueryUI are includded (up to date, stable releases only). Coding with OpenFramework is much FASTER than ZendFramework and MORE SECURE than CodeIgniter, because it uses MultiTier (nTier) Architecture rather than MVC model used in ZendFramework and CodeIgniter. OpenFramework is for professional developers with MultiTier (nTier) Architecture style, which is FAST, SCALABLE, DISTRIBUTED. http://en.wikipedia.org/wiki/Multitier_architecture CodeIgniter is for begginers, with basic MVC style. ZendFramework is for medium developers with clean MVC style. http://en.wikipedia.org/wiki/Model-view-controller Comparison between nTier Architecture vs. MVC Architecture: At first glance, the nTier may seem similar to the model-view-controller (MVC) concept; however, topologically they are different. A fundamental rule in a nTier architecture is the client tier never communicates directly with the data tier; in a nTier model all communication must pass through the middle (logic) tier. Conceptually the nTier architecture is linear. However, the MVC architecture is triangular: the view sends updates to the controller, the controller updates the model, and the view gets updated directly from the model. From a historical perspective the nTier architecture concept emerged in the 1990s from observations of distributed systems (e.g., web applications) where the client, middle ware and data tiers ran on physically separate platforms. Whereas MVC comes from the previous decade (by work at Xerox PARC in the late 1970s and early 1980s) and is based on observations of applications that ran on a single graphical workstation; MVC was applied to distributed applications later in its history (see Model 2). CONCLUSION: nTier is suited for cloud, from small to medium and large client/server applications, since MVC is very comfortable to use MEDIUM developers with minimum training :-)