Desmistifying SOAThis is a featured page

Today, it's very common companies saying "We have SOA", "We have many projects using SOA", "our SOA maturity isn't ad-hoc".

Think about that:

  • Do you really know, what is SOA?
  • Tell more about the Governance, what is the level?
  • How it's possible measure your SOA maturity?
  • How do you know, how many SOA projects do you really have?
  • How is your process of Service Identification & Discovery?
  • How many Searcheable Services in reuse?
  • How many Business Process Services, are in the company?
  • How do you know the impact of SLA, to put more 2 consumers to one specific service ?
  • And your Cannonical Model? How much do you have? How many elements are optionals?

The idea is desmistify SOA, with experiencies in projects, problems, solutions, cases, tips and tricks and much more.

There are many others questions about it. So, an quickly answer for SOA is Service-Oriented Architect. But, SOA is much more.


eprado
eprado
Latest page update: made by eprado , Dec 19 2008, 1:17 PM EST (about this update About This Update eprado Desmistifying SOA - eprado

154 words added

view changes

- complete history)
More Info: links to this page
There are no threads for this page.  Be the first to start a new thread.

Related Content

  (what's this?Related ContentThanks to keyword tags, links to related pages and threads are added to the bottom of your pages. Up to 15 links are shown, determined by matching tags and by how recently the content was updated; keeping the most current at the top. Share your feedback on Wetpaint Central.)