Solved

Deployment Architecture for database server for Web based software  across multiple locations

Posted on 2014-07-31
4
105 Views
Last Modified: 2014-08-11
I have 4  units spread over different geographical location  within a  distance of 100KM radius.  We want to deploy an hospital information system across all the 4 locations. We need to design deployment architecture for the same .

I need the following information from the experts
 
   Which one of the following is better and pros and cons of the same.

    1.  Having a single sql server database instance at a cartelized location (datacenter) and make clients at all the 4  
         locations connect to single instance

   2..  Have a separate database instance at each location.  

  ( There are around 700 clients from all the locations put together (Loc1 - 425 clients, loc2 -  50 , loc3 - 25 and loc4 - 200).
0
Comment
Question by:venkataramanaiahsr
  • 2
4 Comments
 
LVL 39

Expert Comment

by:Aaron Tomosky
ID: 40235212
if you are writing to a database, making it centralized is definitely the easiest route. Otherwise how do you plan on keeping them all in sync?
0
 

Author Comment

by:venkataramanaiahsr
ID: 40237477
What i meant was

 is it better to have separate instance of Hospital information system application at each location talking to location specific db instance and later look for a data warehousing  application for data consolidation  

 (Pros/Cons - i can immediately think of  is this architecture involves less expenditure on networking/connectivity infrastructure)

OR

Is it better to have centralized instance and make all location specific instance of application  talk to central server thro mpls LAN  etc. ( more expenditure on on networking/connectivity infrastructure)
0
 
LVL 39

Expert Comment

by:Aaron Tomosky
ID: 40237580
I would build it as a single database. If it turns out you have performance problems you can't solve except by running multiple copies, then you can try to create a sync program. Syncing can get really hard, especially when dealing with conflicts.

If the db is central, you could do this at the network layer with VPN tunnels or Mpls. However you could also do ssl web services or alternatives at the application layer.
0
 
LVL 28

Accepted Solution

by:
Ryan McCauley earned 500 total points
ID: 40250015
If you've got a reliable network from the remote locations to a central office, then a single centralized database server is the easiest and cheapest option. I'd only look to split it up and put a database at each site for these reasons:

1) Unreliable network - if you can't depend on the remote sites having a connection back to the central server, then they won't be able to use the application when the network is down.
2) Speeds too slow over distance - if your app has constantly database transactions or is written to assume the database is local, it can slow down the app when queries take even a few seconds to come back from the central server
3) Remote sites can't see each others' data - I assume there aren't any data security concerns here, but if you have a situation where each site is absolutely not allowed to see other site's data, then you can put a database at each site that contains only their data. If you can trust you app to keep the data safe, though, it makes sense to locate them all together.

Central is easy and cheap (single server license), and can quickly get complicated if you have to keep things in sync at multiple locations. It would be my design by default unless you had a really compelling reason to put local database servers at each site.
0

Featured Post

Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

This is basically a blog post I wrote recently. I've found that SARGability is poorly understood, and since many people don't read blogs, I figured I'd post it here as an article. SARGable is an adjective in SQL that means that an item can be fou…
SQL Server engine let you use a Windows account or a SQL Server account to connect to a SQL Server instance. This can be configured immediatly during the SQL Server installation or after in the Server Authentication section in the Server properties …
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…

830 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question