Data availability best practices?

  • Thread starter Thread starter Jim Hubbard
  • Start date Start date
J

Jim Hubbard

I have a client that wants me to code a simple application as a prototype.
The catch is that he wants to use this application at several different
stores while being able to share each store's data. He also want the
application to continue to function in the case that the internet is down
for any reason.

I have my own theories as to how to accomplish this shared data environment,
but I'd love to hear your ideas about sharing data real-time (when the
connection is available) and being able to continue to run even when the
connectivity to other stores or a main data storage server is unavailable.

Keeping bandwidth and complexity to a minimum are desired characteristics.

Thanks!
 
I might think about Sql Express at the remote sites and use Service Broker
to pass updates to master site.

--
William Stacey [MVP]

|I have a client that wants me to code a simple application as a prototype.
| The catch is that he wants to use this application at several different
| stores while being able to share each store's data. He also want the
| application to continue to function in the case that the internet is down
| for any reason.
|
| I have my own theories as to how to accomplish this shared data
environment,
| but I'd love to hear your ideas about sharing data real-time (when the
| connection is available) and being able to continue to run even when the
| connectivity to other stores or a main data storage server is unavailable.
|
| Keeping bandwidth and complexity to a minimum are desired characteristics.
|
| Thanks!
|
|
|
 
Thanks William!

This is something that I had not seen yet and looks like a great technology
to incorporate into my apps.

Jim Hubbard
 
Back
Top