Design
Architecture: It's Always a Tradeoff
(This part III of a series -see Part I, Part II)We need to face it -- there are no absolute truths when it comes to software architecture ( I guess that's part of the reason the term always looks so fuzzy. ) Should we use REST? It depends. Should we use OR/M or direct database access? It depends. Sometimes even a big ball of mud can be a good option. The good news is that we can always answer "It depends" to any architectural question and always be correct. The bad news is that it is our role to figure out what does it depend on and come up with a viable trade off.
Related Reading
More Insights
INFO-LINK
To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy. | |