Thought occurred to me when reading Brad Adam’s blog that the names we give services need to be as well thought out as the names used in APIs. I’ve made attempts at this topic before, of course, but I’m wondering if it may be easier just to leverage the work that others like Brad have done on ‘API conventions’ to the world of SOA services.
Apply API design guidelines to SOA?
About the Author: Nick Malik
President of Vanguard EA, an Enterprise Architecture consulting firm in Seattle focused on the Pacific coast of the US. Nick has over 30 years of professional experience in management, systems, and technology. He is the co-author of the influential paper "Perspectives on Enterprise Architecture" with Dr. Brian Cameron that effectively defined modern Enterprise Architecture practices, and he is frequent speaker at public gatherings on Enterprise Architecture and related topics. He coauthored a book on Visual Storytelling with Martin Sykes and Mark West titled "Stories That Move Mountains".