More SOA vs. Web 2.0? I really shouldn't, I'm trying to quit... but OK, just one more.
People must be bored. I am too, it's a rainy Sunday afternoon; what the hey. Last one, I swear.
Anyway, SOA is just a way of building applications so that they are capable of sharing data. REST and SOAP are both protocols for using the services it contains. Web Services are just an implementation of (or wrapper for) those services.
Web 2.0 is allowing other people or systems to participate in the SOA you built. Web 2.0 is the idea of opening systems and allowing others to use them. Google opened its system, all kinds of Google Maps mashups resulted. Flickr opened their system, and mashups resulted. Amazon opened its system, and mashups resulted. "Mashup", is exactly what it implies--it mashes together two different systems and creates a brand new application using the two (or three, or four).
Web 2.0 for the consumer is allowing people to use more than one Web application at a time. People digging a link is feeding Digg's "service" with data. They're just running a fancy report on that data--an interactive report that also uses Digg's services to feed more data into the system. Then digg let's people use that data as part of their mashup.
Web 2.0 for the enterprise is allowing people to use more than one Web app AND/OR internal system at the same time. Web 2.0 for the enterprise will happen when IT departments begin wrapping Web services around existing systems, and start making mashups using THOSE. I can just see the sales pipeline overlaid on Google maps from here.
What will be REALLY cool is when standards start emerging and the data from those services wrapped around the internal systems can be shared with partner companies. Exposing sensitive data, either using. This is going to rock the business intelligence market, I'll betcha. Not only that, but when I had to facilitate data sharing between the company where I was IT Director at the time and our partner companies, I would have absolutely KILLed faor a simple way to share data with them. Instead it always resulted in a 2 week-long project. As Barry Briggs points out, the issue of security needs to be carefully hashed out, and I would imagine some kind of data system partioning done at the enterprise level, but this is still a very exciting time.
Anyway, I digress. SOA is just an enabler. I think I'm done now.