Many IT leaders prefer to buy their application infrastructure software from a single vendor. Â When I was at Burton Group, Anne Thomas Manes and I called the providers delivering comprehensive offerings ‘super-platform vendors’. Â Â In a recent report, Gartner helps teams understand the trade-offs associated with the super-platform vendor strategy, and summarizes the strengths and cautions of comprehensive application infrastructure vendors.
Providing a who’s who in the vendor market, this research offers basic profiles for vendors that qualify to provide a comprehensive set of application infrastructure supporting an organization’s projects in the next three to five years.
Gartner cites WSO2 as a visionary in all three Magic Quadrants for Application InfrastructureÂ including SOA Application Projects, Systematic Application Integration Projects, and Systematic SOA Infrastructure Projects. Of the vendors listed as options in the Comprehensive Application Infrastructure report,Â WSO2 is the only open source vendor included.
Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings. Gartner research publications consist of the opinions of Gartner’s research organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose
I wonder why more open source users do not actively participate in the open source community and become committers or contributors. My open source participation led to a cost efficient and adaptable infrastructure for my company, and useful trade experience skills on my resume. My open source contributions established a professional network of mentors and improved my understanding of the project. Becoming an open source committer enhanced by personal brand, increased business opportunities, and filled important open source project gaps.
Interacting with open source community committers and recommending source code hacks is a valuable experience. During 2001-2003, I had the opportunity to interact with many hard-core, professional open source luminaries (e.g. Sam Ruby, James Snell, Glenn Daniels, Dims, Steve Loughran, and Sanjiva Weerawarana) across multiple organizations while participating in the Apache Axis project. I watched the distributed Axis team advance the project via IRC, code check-ins, and mailing list interactions. After understanding the project’s capabilities and roadmap (by writing many sample code service clients and providers), I gained the knowledge to start directly hacking the source code and contributing useful extensions. My everlasting thanks to Glenn Daniels for nominating me to be a committer! The open source community and committer experience established my open source street creds, raised my personal brand, led to presenting from the OSCON stage (and others), and helped build my consulting business.
When you evaluate infrastructure vendors, do you correlate their agility and innovation with release velocity?
Since teams started creating applications and services, significant challenges have continually hindered effective delivery and diminished development team’s reputations. Common challenges include:
- Long IT solution lead times leading towards anÂ inability to capitalize on business opportunities
- Complex and disjointed development processes hindering IT agility and degrading ability to meet business demand
- Inaccurate project forecasts, non-repeatable processes, and rudimentary performance metrics leading to a persistent Business-IT perception gap
- Perennial tension between management compliance mandates and development approach, whichÂ prevents improving app delivery
How do we change development processes, development tooling, and run-time infrastructure to decrease time to market, streamline development processes, deliver on-time and budget, and meet compliance mandates?
The technoratiÂ and press are touting Apigee’s recent announcement, which declares a free API management offering. Â The Apigee announcement does offer significant end-user value, unless you want to run the API management infrastructure on-premise, or reach critical business mass.
WSO2 has released the first open source API management platform. The platform is a complete solution for publishing APIs, creating and managing a developer community, scalably routing traffic, and securing API content. WSO2 API Manager is released under the Apache Software License 2.0.
For any Government organization needing to do more with less, eGovernment is the answer. eGovernment solutions cost effectively deliver information and enable transactions among citizens residing within a local geography. Â An eGovernment solution may also link various governmental groups supporting constituents. However, the role of eGovernment has been traditionally limited by the inherent cost and complexity of developing, integrating, and managing traditional server-based systems. To overcome these hurdles, government agencies are looking to cloud solutions as a way to radically scale service delivery while simultaneously minimizing the expenses related to IT infrastructure, application development and deployment, and operations. WSO2 has published a white paper examining demands faced by government agencies and how the cloud-native WSO2 eGovernment solution provides a powerful, highly flexible, and extensible platform that addressing eGovernment requirements in a cost effective manner.
For more information, download the paper atÂ http://wso2.com/whitepapers/moving-egovernment-to-the-cloud/
WSO2 Carbon application platform is built on a solid Apache Open Source Foundation.Â Apache Open Source delivers innovative components and an extensive ecosystem of developers, educational resources, and committers.Â Apache projects often surpass proprietary platform vendor offerings, and lead Apache project sponsors (e.g. Google, Twitter, Yahoo, Huawei, AMD) run their Internet scale business on open source project code.
When development teams adopt Apache open source projects, the teams undertake a challenging platform development task list:
- Integrate Apache projects into the application platform
- Synchronize project dependencies and versions
- Maintain build repository and configuration scripts
- Patch project codebase to fix defects
- Upgrade projects and obtain new features
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