SoaIsNightSky is a conceptual analogy for ServiceOrientedArchitecture. Obtaining data from a service is likened to harnessing light from distant stars of varying distance. Just as light from distant stars may take many years to arrive, and therefore reflects a time in the distant past, the data from a service may not reflect the current conditions at the source. Furthermore, the "light" (data) gathered for a local service is used to produce more "light" (data) for consumption at a distant requester. This may raise concurrency issues, especially as services are supposedly autonomous.
For example, a service may issue a status of "Approved" for a given customer. The "Approved" status may pass through the bowels of several other services before being exposed to a consumer. By the time the consumer receives that information, the given customer's status may no longer be "Approved," causing subsequent actions to fail or resulting in erroneous conditions. Obviously, such problems may be encountered in virtually any architecture (traditional ClientServer architecture may be subject to this as well) but may be exacerbated in SOA due to the particularly asynchronous nature of services. This leads some to say SoaIsNightSky.
This notion originated in PatHelland's blog at http://blogs.msdn.com/pathelland/archive/2004/03/18/91825.aspx
The author of the "night sky" metaphor for ServiceOrientedArchitecture got involved in an extended discussion on the nature of services at http://blogs.msdn.com/pathelland/archive/2004/03/22/94000.aspx
A related article entitled "Data on the Outside vs Data on the Inside" can be found at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/dataoutsideinside.asp
See WhatIsSoa SoaAndLooseCoupling