quote of the day from #Gartner’s Eric Knipp about Cloud Native Private PaaS:
“Do you wait around until 2015 (or later) for Java EE 8 to bring you the cloudy features you’re looking for, now that we know for sure that Java EE 7 won’t have any? Or, do you just wait for your preferred IT megavendor to get around to offering you a for-real, multitenant, cloud native Private PaaS that goes beyond simply slapping a pre-built middleware stack onto a virtual machine? ”
The tongue in cheek statements imply that a best-of-breed IT vendor can offer you a Cloud Native Private PaaS alternative today. Check out the Cloud Native Private PaaS architecture underlying WSO2 Stratos – available today.
Recommended Reading for Cloud Native Private PaaS
Cloud Native Private PaaS Architecture
Cloud aware applications and PaaS Architecture
Cloud Native PaaS or Cloud Washed PaaS
The dZone Definitive Guide to PaaS IaaS Solutions delivers a detailed picture of the diverse Cloud landscape and a PaaS Outlook for 2013 (authored by me).
With simple comparison grids and product description pages, complete with unbiased, third-party reviews, you’ll be able to make a well-informed, data-driven decision about the cloud services you want to adopt. The solution you choose is entirely dependent on the types of tasks you want to perform. This guide will help you decide what best fits your company’s needs, and what to look for in the solution you buy.
The PaaS Outlook provides a brief insiders perspective on:
- The importance of Programming Language Support
- Using Cloud-based DevOps processes to accelerate and automate delivery
- The hybrid platform goal state
Cloud platforms exhibiting Cloud Native PaaS architecture provide an opportunity to increase business innovation and creativity. Cloud native platform solutions shield teams from infrastructure details and inject new behavior into the application.
Cloud native PaaS architecture requires infrastructure innovation in provisioning, service governance, management, deployment, load-balancing, policy enforcement, and tenancy. Cloud native, innovative provisioning infrastructure increases tenant density and streamlines code deployment and synchronization. Multi-tenancy within middleware containers enables teams to customize applications and services per consumer by changing run-time configuration settings instead of provisioning new instances.
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.
DevOp teams want PaaS service efficiency with customization flexibility. Rather than fit development teams into a one-size-fits-all platform box, teams desire to extend a PaaS foundation with best-of-breed components, frameworks, and languages. While early 1.0 PaaS offerings (i.e. Google AppEngine, SalesForce.com) prescribed a specific development model and framework set, next-generation PaaS offers a polyglot PaaS and polyglot programming experience, delivering the ability to mix-and-match application platform capabilities into an customized application Platform as a Service (aPaaS) cloud.
PaaS empowers and enables both enterprise IT and shadow IT to accelerate agility and effectively respond to business demands. Do you agree? Chris Keene (@ckeene) has been shaking up the blogosphere, twitterverse, by stating
For most developers, the value proposition articulated by PaaS vendors just doesn’t seem all that different from what they can get from internal IT or external IaaS.
API usage and demand may be unpredictable. Can you scale API infrastructure to meet unexpected peak loads? While you scale API infrastructure, can you guarantee availability and meet service level agreements? Building API solutions on a scalable API management platform will address demand challenges and ensure your API fulfills business demand.
Netflix recently announced an open source Cloud service registry and Cloud load balancer project called Eureka.Â Â Eureka provides NetFlixâ€™s public Cloud movie service with required PaaS framework components that every Cloud-Native environment requires. Â The service registry component tracks dynamic run-time Cloud instances as the PaaS controller spins instances up or tears them down. Client applications or PaaS framework components may access the REST based Eureka discovery service and learn where to direct Cloud service requests, proactively re-configure and optimize Cloud service connections, or reactively re-establish service after component failure. Â Eureka includes a simple load balancer algorithm providing round-robin traffic balancing.
A client posed the following hybrid cloud use case and question:
An customer would have most (if not all) of their back office on-premise currently (i.e. in an data center). Over the next ~5 years, we expect three new scenarios to emerge:
1) back office functionality could move to SaaS (pure public cloud) where the function (billing, inventory management) is delivered as a SaaS resource
2) back office functionality could move to a hosted environment where the back office vendor hosts the application for
3) back office functionality could move to a colo facility where deploys servers in a neutral data center
David Linthicum has an excellent post bashing vendor-driven Cloud thought leadership and Cloud offerings. Daveâ’s summer 2012 outlook on the Cloud Platform market:
“What’s missing is innovation and creativity. There are many problems that still need solving in the cloud computing space, and new approaches should be created to solve them.”