As you probably know and hopefully agree, service orientation is emerging as a dominant way of architecting distributed systems moving forward. And although it doesn’t eliminate or diminish traditional architectural concerns dealing with user interaction, data access and representation, business process implementation, access management and others, it does affect the features and capabilities of their underlying technologies. This fairly recent paper titled “Service Oriented Database Architecture: App Server-Lite?” and written by David Campbell, a long-term member of the SQL Server team, discusses the impact of service orientation on databases using SQL Server 2005 as an example. Specifically, David discusses .NET CLR integration, Database Change Notification, native web services support and Service Broker features of the product and how they can be leveraged in distributed applications to achieve effects of looser coupling, scalability, and interoperability. Please make sure to check out a short list of references at the end of the paper for great additional articles on related subjects.