Re:Clojure and Rails - the Secret Sauce Behind FlightCaster ...
by phildawes on Saturday August 22, 2009 @04:19AM
(#779152)
That's smells a bit of architecture astronaut to me if you don't mind me saying. Sharing information between systems is a tradeoff (vs arch complexity), not something to be avoided at all costs.
Re:Clojure and Rails - the Secret Sauce Behind FlightCaster ...
by smhinsey on Saturday August 22, 2009 @08:43PM
(#780017)
It certainly is not appropriate in every circumstance, but it can make a lot of sense for larger applications where you might have different people or even teams responsible for different parts of the application.
This approach allows you to hide the data models of both parts of the system from one another so you don't end up back in the hell of integrating via the database, which is what I suspect you were driving at with your question. You obviously can't avoid having to share some information between systems, but in this model you can share message and service contracts rather than database schema.