iposner (9/19/2011)
Colin Barry (9/19/2011)
Thought provoking.Why have a service issue the GUIDs? A small bit of clr code could do what you need and would be fast. You could then let your insert stored procedures transparently create the "identity" of the record and return it to your middle tier layer.
Absolutely agree - although SOA may be a buzzword on many people's lips, just because you can do something doesn't mean that you should: Not only does the cross-network and cross-process intercommunication introduce additional latency, but the additional components involved in implementing an additional service reduce the MTBF of the entire system.
Don't confuse SOA with web services. In this case - "service" is just as valid a name for the CLR code as if would be for the web service call previous advocated. SOA also has nothing to do with whether the functionality is "local" or "remote".
In short - both would be SOA if the purpose is reusability of the identifier (GUID) functionality.
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?