synchronization - Synchronizing data between server and client -
when comes mobile applications lot of time client going offline.
right when user submits data on client saved locally , when press sync button pushed , pulled between client , server.
what best practices when comes synchronization of data?
server side have large ms sql server , client side have sqlite @ hands.
you might find this (this microsoft application architecture guide v2.0, oct 2009) useful. facing same problem here @ work, , i did find these guidelines useful in process of thinking.
to share experience, think major decision comes problem trying solve. if you're facing single, fixed, mature business domain (i.e, changing db schema , face 1 or 2 clients) can build own data synchronization framework. far better using commercial or non-commercial frameworks in terms of ease-of-use , adjustment + performance. + store-and-forward feature can overcome connectivity issues.
however, if facing changing (not expanding) business domain, or maybe different clients different requirements might want use mature framework (like microsoft synch framework) parts of work , can focus on adjustments needed requirements.
i hope isn't general.
Comments
Post a Comment