Summary of trade-offs, UltraLite vs. M-Business XML datastore

The decision on whether to use UltraLite or M-Business XML datastore depends on the needs of the developer.

UltraLite is a robust database solution with a high-performance synchronization engine that will scale for thousands of users. UltraLite has features, like indexing, which allow searching and improved responsiveness with much larger datasets, rich dynamic SQL support, transaction processing to comply with the existing enterprise rules, and other features expected of a full-featured database. MobiLink also offers robust, flexible bidirectional synchronization with enterprise data stores.

The M-Business XML datastore is simple to develop with but provides only one-way synchronization of data. Its main advantage is that it does not require a preloaded schema on the device.

The table below summarized the trade-offs between UltraLite and M-Business XML datastore.

For more information on UltraLite, see UltraLite M-Business Anywhere Programming and UltraLite tutorials, referenced in Related publications. The sample that follows is focused on recently introduced features that improve the deployment and user experience of using these technologies.

For more information on the M-Business XML datastore, see Using M-Business XML Conduit and API, and Building Applications with M-Business XML Conduit.

Table 1. Comparison of UltraLite and M-Business XML datastore

Feature

UltraLite on-device database

M-Business XML datastore

Basic functionality

Full-featured RDBMS: indexes, referential integrity, transactions (rollbacks and commits)

Minimal datastore: simple to develop with but provides only one-way synchronization of data and does not scale well for large data volumes

Flexibility

Very flexible; can be configured in many different ways

Limited flexibility

Ideal back-end datastore

Enterprise database (Oracle, MS SQL, DB2, ASE, SQL Anywhere, etc.)

Back-end datastore that can emit XML upon receiving an HTTP request

Interface to back-end database

Standard DB interface (ODBC); highly efficient

Custom XML data stream; inefficient

Scalability

Scales easily for thousands of users

Limited scalability

Simple for those familiar with...

SQL and relational databases

XML and ADO

Simplicity of use and provisioning

More complicated: pre-defined schema required for synchronization with MobiLink

Relatively simple: no schema required

Synchronization

Two way; extremely efficient

One way; requires HTTP forms and conversion of back-end information into a specific XML format for upstream data; inefficient


UltraLite POD for SQL Anywhere 10