You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How practical would it be to implement a cluster provider that doesn’t rely on a central db? Each of the nodes in this system is aware of each other through existing configuration. The architecture does not currently require a database and has up to this point relied on WCF P2P to avoid the need for a database. I’m trying to remove the WCF dependency. I’ve considered implementing a provider based on in memory where the membership table is bootstrapped with the known configuration but there are properties such as generation id that aren’t consistent. Maybe this known node (effectively seed nodes) scenario is a square peg for a round hole…
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
How practical would it be to implement a cluster provider that doesn’t rely on a central db? Each of the nodes in this system is aware of each other through existing configuration. The architecture does not currently require a database and has up to this point relied on WCF P2P to avoid the need for a database. I’m trying to remove the WCF dependency. I’ve considered implementing a provider based on in memory where the membership table is bootstrapped with the known configuration but there are properties such as generation id that aren’t consistent. Maybe this known node (effectively seed nodes) scenario is a square peg for a round hole…
Thanks,
Ross.
Beta Was this translation helpful? Give feedback.
All reactions