{

Microsoft has a new article (you need it!) concerning SOA (Service Oriented Architecture).

Interesting responses on my Joel On Software post:

Service Oriented Architecture is really a tool more focused on enterprise IT. It's for exposing a companies "business logic" through software. It's not really a concept for applying to a stand alone application like fogbugz or Word or whatever.

Service Oriented Architecture is really a tool more focused on enterprise IT. It's for exposing a companies "business logic" through software. It's not really a concept for applying to a stand alone application like fogbugz or Word or whatever.

If you're a company who has a business such as finance, healthcare etc, you have an IT department who has built custom software which contains your business logic. For many reasons you want to expose that business logic in a generic way so that it can be easily consumed:
1) by other pieces of internal software
2) by external software of your clients
3) by partner companies or companies your might merge with
etc...

And it stands as an important question exactly what type of software one is writing then; I agree that in many organizations SOA (I've worked at gigantic places like Intel and Countrywide and they surely have use for it) is important but I find it hard to believe that it would be as ubiquitous... I'm going to take a back seat and start studying the architecture more and comparing it to the work I've already done and seen in the "enterprise."

}