Sign in or 
| Version | User | Scope of changes |
|---|---|---|
| Dec 19 2008, 1:17 PM EST (current) | eprado | 154 words added |
| Dec 19 2008, 12:50 PM EST | eprado |
Changes
Key: Additions Deletions
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:
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.
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.
