|
|
|
|
 |
| Tech Update |
|
Native XML databases boost e-business transaction speeds
Are they for you?
By Maggie Biggs
November 9, 2001
[an error occurred while processing this directive] |
To determine if your company should implement a native XML database, consider which data sources you have that might require XML translation. If you have more than one data source that you will use for XML-based applications, a native XML database might be in order. Moreover, if you have large groups of data that require XML translation, a native XML database is also an attractive option to minimize the impact of translation processing. XML databases include application programming interfaces (APIs) that you can use to integrate XML data with application.
For example, you might need to exchange data with other companies using XML to support your billing and payment processes. This data might be stored in one database. At the same time, you might need to exchange XML data with other companies to support online ordering and product shipments. These applications might use an entirely different database or even data stored in your file system.
A native XML database--implemented on the middle tier, usually along side an application server--would allow you to process XML translations for billing, payment, ordering, and product shipment on-the-fly or in batch mode without impacting either of your back-end databases, your file system performance, or the speed of your Web applications.
 |
|
|
|
|
![]() |
|
[an error occurred while processing this directive] |
![]() |
|
![]() |
[an error occurred while processing this directive]
|
|
[an error occurred while processing this directive]
|
|
|
|
