|By Cloud Ventures||
|March 1, 2014 08:08 AM EST||
Probably the most impactful way to describe the potential and impact of Cloud Identity technologies and the IRM concept (Identity Relationship Management) is through starting to look at how these trends will modernize the SOA (Service Oriented Architecture).
A while back I proposed an idea of the ‘D-SOA’ – Distributed SOA, based on the principle that in the XML Web services world the enterprise architect would move from writing software that addressed other software within their own corporate domain (SOA), they would evolve to addressing this and also domains outside of the corporate control (D-SOA).
This would be facilitated by federated identity and naming protocols like XDI, and bring about a Cloud Naming System.
I think we’re seeing that effect become real now, and it’s also worth modernizing the term now and proposing the C-SOA model, to reflect the overall Cloud environment.
Rackspace introduces the C-SOA model in our second issue of TRANSFORM, where we describe how it could be applied to the Canadian Healthcare sector.
Increasingly we will also see the use of ‘Certified Cloud Computing‘, and a great couple of examples of how all these effects are becoming manifest is via:
- an Edinburgh Identity startup called Miicard: Certified Bank Statements
- Cardwise : Xpenditure – Corporate expense apps
Both demonstrate the ‘apps store innovation’ that is ongoing and how slick apps like this are taking on specific process-centric apps that make best use of the slick features of smartphones, and then integrate with back-end corporate ERP systems.
Federated identity mechanisms on the device will be one of the key ways security is achieved and enabled, and will therefore provide a platform for trusted ‘building blocks’, such as “iPayments” for example.
They’re trusted because they are Identity-enabled, and then also Certified as well, so the use of surrounding ‘Trust Frameworks’ are key too.
Increasingly as more merchants join these environments so it will increasingly become end-to-end. The expense app for example still has to take a photo of a receipt to then use it digitally, when really the retail POS should generate a digital one first that is then transferred to the customers account via Identity mechanisms.
These transactions require this cross-domain activity and hence the role of C-SOA in this equation.
The post iPayments – An example of utilizing C-SOA and ‘Certified Services Architecture’ appeared first on Cloud Computing Best Practices.