All geek questions in one place

SQL Server Replication Best Practices

We have a script

One main e-commerce website - currently attracting many visitors.

Three fall under the "brand specific" sites that will hang from this site - each of these sites will have the same level of traffic over time.

The client requires that order processing for each brand website take place in one place (i.e. one back office).

What topology should we choose? We believe that it is possible that with the main sql server with reading and writing from backoffice and replicating this data to "brand-specific" instances of the SQL server, it can work. Each particular brand will have its own dedicated sql server for Frontoffice “reads”. Any records we make will be returned to the main database to support parallel content

Any thoughts? Future scalability is a major factor.

+3
source share
2 answers

Without a more detailed understanding of how your application should function, it is difficult to provide you with a clear direction.

(Publisher), , () , , . , , , .. , , , , .., , , .

, , , , . , , .

, . , , , .

, , , , .

,

+1

, Youtube scaling - youtube. , .

0

Source: https://habr.com/ru/post/1702695/

More articles:


All Articles