Hello,
I wanted to kindly ask about the differences between AlwaysOn and ReadScale, regarding the following context:
- We have a live Business Central Server and now want to create replicas of it, for various apps to hit them instead of the live (of course, this means that "real time" sync is a paramount)
- For this, we were trying the Transactional Replication, but since we wanted to mirror the Server settings also (not just the data(bases)), we decided to look at Availability Group Clustering
- I am aware that there are two options when it comes to Availability Groups
- AlwaysOn (requires an underlying WSFC)
- Read-Scale (no Cluster Manager required)
However, since I have no prior experience with Clustering, I am trying to avoid spending days on trying to set up something I will end up having to replace, so, please, if you could point me to the right direction:
- In general, practical terms, what is the difference between the AlwaysOn and Read-Scale (apart from the Cluster Manager)
- If I do not need the overhead of the HA solution, but just want the server settings and the data to be mirrored to n number of replicas, would Read-Scale suffice (or what I want is intrinsically tied to an HA solution, hence the Clustering)?
- If you have any other advice regarding an optimal solution, please do share.
With thanks and kind regards,
Bogdan
BogdanU