Making the Case for Local Database and Synchronization
When you have mobile workers that need to read and write from a database, you have some tough decisions to make. Where should the data be stored and how should it be transmitted? A smart client architecture might provide the right balance for your applications.
by Martyn Mallick
March 17, 2003
Editor's Note: Martyn Mallick is a wireless solutions evangelist at iAnywhere Solutions, a vendor of mobile database solutions. Though the article is not impartial, we have sought it for publication because we believe there is educational value in the technical concepts as presented.
hen extending information to mobile workers the first problem that the IT department has to solve is how to give those workers access to enterprise data when and where it is needed. Smart client applications have emerged as the architecture of choice over browser-based wireless Internet applications, as they enable access to data while the mobile user is disconnected from the networkwireless or otherwise. This capability is best implemented by incorporating persistent data storage using a mobile database in your application.
Your choice of mobile data storage will dictate many factors of your mobile application including storage capacity, performance, security, operating systems support, development tool support, and ability to integrate with enterprise data sources via synchronization.
It's quick, easy and you get access to all the articles on DevX.
This registration/login is to allow you to read articles on devx.com. Already a member?
To become a member of DevX.com create your Member Profile by completing the form below. Membership is free!