 |
|
|
 |
The HorizonJ architecture is intended as a flexible base solution for commonly encountered architecture challenges involved in building J2EE applications. The primary goal of HorizonJ is to dramatically simplify the amount of effort required to design, develop, and maintain complex systems. However, HorizonJ does not force users into proprietary constructs. Often, productivity toolsets require use of proprietary languages and development tools. Too often, these proprietary frameworks only address a subset of what is required, and do not easily enable you to work outside of their constructs to create the solution you need. At a certain point, more time is spent fighting the tool than gaining benefit from it.
JSoft believes that it is important to provide functionality without locking designers and developers into an overly rigid framework. The entire HorizonJ design philosophy centers around providing value by offering architecture solutions without restricting use of alternatives. For example, HorizonJ design patterns are largely described by Java Interfaces, accompanied by HorizonJ implementations of these interfaces. In most cases, the default functionality (e.g. how does a business object persist to the database) is sufficient. However, your software team is able to provide their own implementation if necessary simply by following the HorizonJ interface specification.
|
|
|