|
|||||||||||||||
|
|||||||||||||||
|
|
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
xTier Products:
xTier/LWC 2.3 for Java The components that comprise xTier/LWC 2.3 for Java are bundled together in a light-weight container that provides a single point of integration, and centralized component configuration and administration. Developers experience a significant productivity gain as compared to using multiple single-functionality products because the developer is no longer responsible for multiple integration points, configuration and administration methods. Although all of the services in xTier are part of the same container, xTier has very few internal dependencies. In fact, developers can use the individual components as dictated by the technical requirements of the project rather than changing the project architecture to fit xTier. Rather than developing the functionality contained within xTier in house, or spending valuable development time and effort integrating a number of different products from multiple vendors, the enterprise developer is free to concentrate on developing business value for their organization.
xTier 2.3 for Java includes:
xTier/GRID 2.3 for Java It is important to note the difference between on-demand computing and computational grids. On-demand computing generally enables on-demand provisioning of IT resources - CPU load, data storage, network bandwidth, etc. These resources can reside within the enterprise (co-located), reside within data centers that are not physically at the business premises (outsourced) or be provided by on-demand (a.k.a. utility) computing providers. Computational grids on the other hand concentrate on solving a specific type of business task - one that is computationally intensive and can be logically split into parallel sub-tasks that can then be asynchronously executed and then the results aggregated together. The confusion between on-demand computing and grid computing is that in most cases computational grid implementations employ an on-demand strategy for the allocation of the computational resources that the sub-task execution is delegated to. In other words, computational grids often use on-demand infrastructure when matching resources to computational load. xTier/GRID is built upon the many of the services provided within the base infrastructure provided by the base xTier and uses many other xTier services for its operation. It uses cluster service to manager grid node topology including automatic topology discovery, topology change management and general resources allocation. It uses marshal service for cross-platform provisioning of grid task units and their result aggregation.
xTier/GRID 2.3 includes:
xTier/CACHE 2.3 for Java To achieve high-performance on invalidations, the xTier Cache Service provides full two-phase-commit ACID transactional support that can be used when using either plain JDBC to access the underlying database, or alternatively, can be effectively integrated into any JTA environment. Another important feature of the xTier Cache Service is the introduction of depended objects that can be used, for instance, to efficiently cache query results. With the introduction of xTier 2.0 for Java, the xTier™ Cache Service provides a JCache (JSR-107) compatible API as well as the native xTier API. The difference between these two interfaces is that the JCache compatible API (as per JSR-107) utilizes unchecked exceptions, while the xTier native implementation utilizes checked exceptions. This provides the developer with great flexibility when implementing distributed object caching.
xTier/CACHE 2.3 for Java includes:
xTier/CLUSTER 2.3 for Java
xTier/CLUSTER 2.3 for Java includes:
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
Copyright © 2004-2008 Fitech Laboratories. All rights reserved. Legal and privacy notice. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||