Hi, in our company each developer has developed over a long time on its
own applications and we have a large legacy database which every
developer added things he need to its own purpose without looking for
the entire thing. Its a mess and i want to start to correct that thing
over time.
So now i want start to introduce messaging and CQRS and my question is:
What are the best strategies to manage endpoints and message types over
multiple applications without getting lost?
While thinking about it, i have a problem with sharing assemblies
because you have to update each application if you change one message.
With something like protocol buffers serialization would that be handled
a lot better since i only need to share the contract file which are very
simple. And protocol buffers has its own versioning story within.
-Steve
--
You received this message because you are subscribed to the Google Groups "Rhino
Tools Dev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/rhino-tools-dev?hl=en.
