Old forum URL:

st3fanus posted on Thursday, November 24, 2011

Hi all..


I want to build distributed application on several location, and which is the best one :

     use one database server on central office and each branch office has application access those server remotely for real time usage


     each branch office has a database server for work locally so that branch office has better performance access and then synchronize to database server on central office


the case :

1. any real time transaction that central and branch need to know those information ( like mutation , etc )

2. there is a transaction that can be sent into central office on evening ( for example : sales order, etc )


Could anyone give me a suggestion ?

I confuse which architecture i should choose ??

If  you need more information let me know (  I'm sorry if i difficult to describe the scenario )


thanks a lot

JonnyBee replied on Sunday, November 27, 2011

I  prefer to have one common database and a farm of stateless application servers (to scale up for performance).

Having distributed database servers and replication is a lot more work to adminstrate.

Yes, that architecture may require some extra care in designing your app and messages/UOW objects.

st3fanus replied on Monday, November 28, 2011

Hi jonny, thanks for your response


Yes, I'm agree with you about a lot of work to synchronize the database.

I'm sorry , I still not understand about :

1. "a farm of stateless app servers"

2. that architecture may require some extra care in designing your app and message


could you explain / with an example, so i can understand those ?


thanks a lot

Copyright (c) Marimer LLC