c# - .NET architecture design issue -


im starting work on particular piece of development.

we have .net wcf application, mysql/ef dal/orm, called threaded job scheduler pulls data 1 client, stores in our db , passes latest data client , vice versa.

so think messages,

clientb sends order clienta through our system transforms order readable format clienta.

clienta can send messages clientb through our system stuff "your order shipped" or "your order late".

i need take these messages , relay them onto clientb want transactional , have full control on failed messages etc.

my current thoughts are, simplicity sake, have ordermessages table in our db receives messages, state of "ready" can processed factory , forwarded relevant client using configuration stored against clients.

sorry being on place, i've explained im trying :/

neil

your proposed architecture classic queue table pattern. remus rusanu canonical resource building such thing sql server. ideas apply other databases well.

there nothing wrong architecture. note, in case of error when messaging client cannot know whether message received or not. there no 100% solution problem. 2 generals problem.

if make clients pull directly database can avoid problem. clients can use own transactions in case.


Comments

Popular posts from this blog

c++ - QTextObjectInterface with Qml TextEdit (QQuickTextEdit) -

javascript - angular ng-required radio button not toggling required off in firefox 33, OK in chrome -

xcode - Swift Playground - Files are not readable -