Extreme transaction processing
It has been suggested that this article be merged into transaction processing. (Discuss) Proposed since January 2010. |
It is proposed that this article be deleted because of the following concern:
If you can address this concern by improving, copyediting, sourcing, renaming, or merging the page, please edit this page and do so. You may remove this message if you improve the article or otherwise object to deletion for any reason. Although not required, you are encouraged to explain why you object to the deletion, either in your edit summary or on the talk page. If this template is removed, do not replace it. This message has remained in place for seven days, so the article may be deleted without further notice. Find sources: "Extreme transaction processing" – news · newspapers · books · scholar · JSTOR Nominator: Please consider notifying the author/project: {{subst:proposed deletion notify|Extreme transaction processing|concern=Article appears to be completely unsourced and completely unnecessary, but I can't see the G6 that was applied to it as being at all in accordance with process}} ~~~~ Timestamp: 20130125063049 06:30, 25 January 2013 (UTC) Administrators: delete |
Extreme transaction processing (XTP) is an exceptionally demanding form of transaction processing. Transactions of 10,000 concurrent accesses (500 transaction per second) or more would require this form of processing.[citation needed]
Description
XTP applications are designed, developed, deployed, managed, and maintained on computer clusters and/or distributed grid computing networks. As a result, XTP applications feature vast improvements in:
- performance
- scalability
- availability
- security
- manageability
- dependability
These applications generate orders of magnitude more transactions than those created by traditional transaction processing systems because of their wider (often multi-enterprise, national and global) reach.
Methodology
This section is empty. You can help by adding to it. (July 2010) |