In SQL 2008 R2, I understand that Peer-to-Peer replication can provide a unique opportunity.
I'm currently looking to understand if this capability feeds into an application architecture I'm beginning to research a concept for.
My firm is a medical device manufacturer. We are looking to build a new medical device gateway. This gateway is pretty simple in that medical devices connect to the gateway to transfer device operation information (little (1000 character) XML formatted
messages, several hundred messages per minute).
In our legacy design, we have N+1 application servers, load balanced, that the medical devices communicate to. These gateway application servers send and receive XML messages to the device, and persist the messages into an Oracle 10g database (boo hiss!)
The current architecture is redundant at the application server level with load balancing, but the DB is the single point of failure.
In drawing up a concept of a new gateway, I was thinking of a design where each node of the application gateway consisted of the application services for device communications as well as MS SQL 2008 R2 Std configured as peer to peer replication between
each node (two, three, or maybe four nodes max).
So my thought was to use load balancing to have a device connect to a node in my new gateway, transmit the XML statu
View Complete Post