We have a set of common entities which are 'shared' throughout the company - much like Master Data Services (MDS) data. Everyone has differing ways of maintaining said data...most of which are painful and/or lacking.
So...I created a working 'demo' using the SQL Service Broker (SSB) to show how we can easily & seamlessly propagate the 'shared' data. Of course, this data is centrally managed & applications (themselves) do not change said data.
Another person wants to use SignalR to propagate the 'shared' data to application databases. And, I love SignalR. However, to me, SignalR is "real-time" front-end "componentry"...not a data transfer service solution for MDS-styled data.
I see the broker as the right tool for this job. And frankly, to me...just because you CAN do something...doesn't mean you SHOULD. But I am open to being wrong.
(1) Am I wrong or right.
(2) If so, why or why not?
Thanks for the help.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
We have a set of common entities which are 'shared' throughout the company - much like Master Data Services (MDS) data. Everyone has differing ways of maintaining said data...most of which are painful and/or lacking.
So...I created a working 'demo' using the SQL Service Broker (SSB) to show how we can easily & seamlessly propagate the 'shared' data. Of course, this data is centrally managed & applications (themselves) do not change said data.
Another person wants to use SignalR to propagate the 'shared' data to application databases. And, I love SignalR. However, to me, SignalR is "real-time" front-end "componentry"...not a data transfer service solution for MDS-styled data.
I see the broker as the right tool for this job. And frankly, to me...just because you CAN do something...doesn't mean you SHOULD. But I am open to being wrong.
(1) Am I wrong or right.
(2) If so, why or why not?
Thanks for the help.