Service Oriented Architecture (SOA) Notes
November 14, 2006

Focus: This Interchange focused on several areas of service oriented architecture from “What Do You Do To Get Started?” to Interoperability Standards”.

What is SOA?
-Taking a step back and looking at solutions differently.
-Realizing that no application lives on its own.
-Standards based systems that are used to talk to each other. They use a method called coupling to actually do the talking.
-In restriction comes value.

How do we get our developers on board?
-Show them the new tools and technology.
-Explain that this process will make their jobs easier in the long run.
-Gives them more opportunities to gain more education.

Key Ideas that were discussed:
-Object oriented deals with things, behavior, and SOA does not change behavior because technologies can still talk to each other.
-Microsoft deals mostly with .net and has easy ugrade paths. You can write the code once and then choose how to expose it.
-Bu- in from executives is crucial for funding and setting precedents to the rest of the company.
-Start with the system that causes you the most problems and work your way up from there. Do not try to do it all at once.
-Allow the “bus” to manage standards and policies.
-Using in-house developers.
-QA testing helps show and add value everyday.