Many on the planet of cloud computing think about cloud computing as a new space that requires new requirements. The reality is, most of the requirements we've worked with on the planet of SOA over the past few years apply to the world of cloud computing. Cloud computing is just a modification in platform, and the existing architectural standards we leverage must transfer well to the cloud computing area.

SOA Standards are a double edged sword

They plainly offer some value by protecting you from vendor-specific requirements, in this case, cloud lock-in. However, they can postpone things as business ITs await the requirements to emerge. In addition, they might not live up to expectations when they do arrive, and not provide the anticipated value.

 

 

Standards should be driven by existing innovations, as opposed to by trying to define new requirements methods for brand-new innovations. While the latter does sometimes work, more frequently it causes design-by-committee and poor technology. Past failures around standards should make this less of a concern on the planet of cloud computing.

 

So, when considering SOA and cloud computing requirements, take a few things into factor to consider:

Standards needs to be driven by 3 or even more technology vendors that really plan to utilize the standard. Watch out for requirements that include simply one supplier and lots of getting in touch with organizations. Or, are simply driven by advertising and marketing.

Standards should be well-defined. This suggests the devil is in the information, and a true standard should be defined in detail all the way to the code level. Theoretical standards that are absolutely nothing however white documents are useless.

Standards should be in wide use. This indicates that numerous tasks leverage this requirement and the technology that uses the requirement, and they succeed with both. In many instances you'll discover that standards are still ideas, and not yet leveraged by innovation consumers.

Standards must be driven by the end individuals, not the suppliers. A minimum of, that's the means it ought to be in a best world. While the suppliers could have had a hand in producing the standards, the customers of the innovation must be the ones driving the meaning and direction. Standards that are defined and kept by vendors frequently fall short to catch the hearts and minds, while requirements kept by technology customers typically offer more value for the end user and thus live a longer life.

SOA Standards