He notes optimistically that:
IT managers can do what they do best — worry about scalability, uptime, security and standards compliance on the back end or in the backbone — and leave many of the use cases for users themselves to sort out.I saw "optimistically" because of the worry many IT managers would have that BYOA is simply a way for employees to circumnavigate IT departments, and avoid their pesky concerns about security and standards compliance. But surely IT departments should embrace BYOA. How? By ensuring that the BYOA apps run through an on-premises Cloud Service Broker . The CSB layers on the attributes which may be lacking from from a BYOA app. These are rules for monitoring scalability and uptime (see the piece on "It's 4am - do you know where your Cloud provider is"), as well as security and standards compliance. And what about mobile BYOA apps that aren't run from inside the enterprise? Those BYOA apps can be run through a Cloud-based infrastructure, leveraging "reachback" into the enterprise, as described here in this webinar.
One fascinating aspect of Podio is how it is a Cloud app, itself built on a stack of Cloud apps (Amazon CloudFront, on Amazon Web Services, with Zendesk). So you can built your own BYOA Cloud app on top of a Cloud service (Podio), which itself is on top of Cloud services (Amazon's). It's turtles all the way down, and I think we'll see apps like this increasingly in the future. Clouds on top of clouds. Podio is on Amazon, so an Amazon outage affects it. Its customer management is with Zendesk, so ditto. A Cloud Service Broker can monitor and manage this.
By the way, the next trend? BYOI: Bring Your Own Identity. A future post on that...