Cloud API popularity is fueling interest in creating service ecosystems across organizations, teams, and applications. By externalizing software platform functions from containers, operating systems, and on-premise data center environments, new business opportunities emerge, and development teams gain faster time to market when building scalable business solutions. Is the time right for you to build a cloud ecosystem architecture based on APIs and supporting rapid application development?
ALM PaaS bridges the development gap between corporate IT and distributed outsourced development activities. The traditional gap impedes system integration, user acceptance testing, visibility into project progress, and corporate governance. Stephen Withers describes an often true, and ineffective current ALM state:
” the CIO does not have visibility of the overall project: this is a major problem.”
A top CIO desire is to obtain portfolio-wide visibility into development velocity, operational efficiency, and application usage.
What solution or best practices do you see solving balkanized, silo development tooling, governance, workflow, and status reporting across distributed outsourced teams? Does your desired solution integrate with tools a CIO’s outsourced organizations are using?
Open source PaaS, Open APIs, and Open Ecosystems are accelerating agility, empowering developers, and enabling innovative business strategies. In a recently published white paper, I describe how adopting a New IT plan can create a responsive IT team.
The path to New IT requires moving away from traditional application platforms, traditional team structure, and traditional information flows. Responsive IT teams are adapting their infrastructure, processes and tooling to re-invent the application platform and re-think application delivery. The New IT architecture underlying Responsive IT intelligently incorporates Cloud Platforms, BigData Analytics, Enterprise DevOps, and API first development.
How are you building a pragmatic, open source driven game plan that incorporates New IT approach vectors, Open DevOp PaaS, Open APIs, and Open Ecosystems?
InfoQ has posted the presentation video for my Building a Cloud Ecosystem Architecture presentation.
The abstract for the presentation:
Offering a business capability as a one-size-fits-one solution is a typical IT solution trap. One-size-fits-one solutions do not exhibit the adaptability or agility required to fulfill new business opportunities. Teams are intrigued by the cloud’s promise to create a one-size-fits-ALL solution. Implementing Cloud architecture concepts to build an ecosystem platform and a vertical Platform-as-a-Service (PaaS) will accelerate the IT team’s ability to deliver solutions that support business growth objectives. A cloud ecosystem platform enables teams to deploy context-aware solutions, rapidly provision 3rd party application projects, automate governance approval tasks, ensure regulatory compliance, monetize user interactions, and host applications that seamlessly extend the user experience. By hosting all business partners as tenant applications within a multi-tenant environment, the ecosystem environment more readily aggregate and share business information.
In this session, Chris will describe:
- Why ecosystem platforms and tenant personalization increase business agility.
- When to extend the user experience by architecting multi-tenant, context-aware cloud applications and APIs.
- How frameworks and containers are evolving to deliver a multi-tenant environment from data to screen.
- How a vertical Platform-as-a-Service ensures regulatory compliance, automates governance approval tasks, and more readily shares business information and capabilities.
API developers are ready to stage a mutiny. Will the captains of Twitter, LinkedIn, and NetFlix make developers walk the plank?
During early market colonization days by Twitter, LinkedIn, NetFlix, Pinterist, and Instagram, the companies prioritize customer land grab over trade and commerce. Web 2.0 companies often choose to build distribution channels first.Â The accepted navigation route includes courting third party developers with Open APIs and pseudo Open Data.Â Â The data is freely available, readily accessible, and governed by limited commercial terms of service.Â Â The corporate path to monetization is through advertising and light data API linking rather than building a deep ecosystem platform. However, with smart API developers creating better customer experiences and challenging revenue growth, the company captains have decided to change the terms of service and limit third party API developer participation.Â All actions show the companies attempting to monetize their valuable asset and gain more gold coin, while limiting access by privateers.
As business leaders focus on growth during 2012, they are identifying business expansion and transformation opportunities. The resulting IT mandate to rapidly evolve mobile and social interactions is forcing CIOs to re-invent their software delivery. By following a straightforward four-step plan, CIOs can improve productivity, enhance agility, deliver timely solutions, and help fulfill strategic business growth goals.
Application development organizations continue to undergo a structural shift towards business enablement and away from technical debt. Teams desire to re-invent software delivery into an agile, on-demand application environment and change the business-IT dynamic. WSO2 platforms enable IT to solve mundane technical plumbing and focus on business-oriented personalization, self-service, monetization, and analytics. When changing the business-IT dynamic, we see leading clients:
- Share infrastructure and improve internal software delivery
- Enable on-demand digital disruption via ecosystem platforms
Related Reading: DevOps Meets ALM in the Cloud – Cloud DevOps Factory
Pinterest is being touted as a web ecosystem platform that may potentially rival FaceBook.Â To be a web ecosystem platform, an online website property publishes an API enabling an ecosystem of 3rd developers.Â Â Once Pinterest publishes an API, 3rd party developers could extend core Pinterest functionality, enrich the user experience, and accelerate user adoption.Â Â Â According to recent reports, Silicon Valley entrepreneurs and investors are ready to ride user interest in Pinterest:
â€œWhen the API is available, Adam Ludwin at RRE, says he’s interested in entrepreneurs who can build on top of the platform, who can “close the loop” and figure out a way to monetize the interest around products on Pinterest. He’s interested in startups that will provide tools to facilitate transactions on and through Pinterest.â€
But exposing an API can lead other companies capturing revenue otherwise directed to Pinterest.Â Â As reported recently by Jay Yarow, Pinterest
â€œmight not release it [API] for a while, says an industry source familiar with Pinterest’s plans. This source says that Pinterest fears having a â€˜Twitter problem.â€™â€