Tag Archives: PaaS

Collaborative

ALM PaaS Bridges the Dev Gap

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?

Continue reading

Reducing Cloud Computing Cost

Warning: Cloud projects may cost more than terrestrial projects. Cloud projects may not reduce IT cost.    Unless, you carefully consider appropriate Cloud usage scenarios, build Cloud-aware solutions, and choose Cloud-native platforms.

Jared Wray (@jaredwray) has obviously been thinking about Cloud’s value proposition, market awareness, and end-user adoption scenarios. Jared has penned an excellent post on Cloud computings hidden costs that delivers in-depth analysis on Cloud computing dynamics.

Many news writers have documented cloud’s hidden cost, for example Beth Pariseau (@pariseauTT) at SeachCloudCOmputing documenting cloud sticker shock.    Beth outlines a key areas to watch:

  • Server instance performance
  • Provisioning cost
  • Data storage cost
  • Distaster recovery,  monitoring, and network bandwidth

Why Be Concerned About Cloud Cost?

Archana Venkatraman (@archanatweets) posts in ComputerWeekly that a

global survey of CIOs into attitudes and concerns relating to cloud computing has revealed that almost 80% are concerned about the hidden costs associated with cloud computing.

Adding to the conversation, Joe Mckendrick (@joemckendrick) details specific points of concern:

  • Poor end user experience due to performance bottlenecks (64 percent). This goes right to the customer end-user experience as well, since e-commerce is the leading cloud application area, the survey finds  – 78 percent of respondents are already using cloud resources to support e-commerce.
  • The impact of poor performance on brand perception and customer loyalty (51 percent).
  • Loss of revenue due to poor availability, performance, or troubleshooting cloud services (44 percent).
  • Increased costs of resolving problems in a more complex environment (35 percent).
  • Increased effort required to manage vendors and service level agreements (23 percent).

Correlating hidden cost fears,  IBM’s recent admission that  Cloud Foundry demand is “in its infancy” (reported by Joe Curtis  @JoeCurtis_CBR), and a 2013 summer story of lagging Enterprise PaaS adoption, many  IT professionals may predict that

PaaS may be poised to enter the trough of disillusionment.

The Smart Cloud Path Forward

Fortunately, smart tech leaders are presenting a viable path forward.  A path that jumps over the disillusionment gulf.  I especially appreciate Jared’s statement,

most savings come when users take advantage of the platform to optimize their workloads. 

When workloads and the platform may become Cloud-aware, Cloud solutions can live up to the hype.  Successful teams optimize code, configuration, and policy to capitalize on Cloud-native architecture and capabilities.   Rather than a ‘Bigger in Texas’ design mentality, a frugal, just-enough at the right time, design must pervade the Cloud solution.   I would like to see the industry move towards benchmarking how multi-tenant design effects ‘tenant density’ (tenant count divided by granularity), scaling time lag, and solution cost.

Reducing Cloud Computing Cost: Recommended Reading

PaaS TCO and PaaS ROI: hared multi-tenant container PaaS 

Building Multi-Tenant SaaS Applications 

Cloud-Native PaaS Architecture

Hidden Cost of Cloud Computing  (Joe Mckendrick)

Where is the Rub: Cloud Computings Hidden Costs (Jared Wray)

 

Creating a SaaS App with the Multi-Tenant Carbon Framework – Step 1

When using traditional application servers and integration middleware, developing a multi-tenant SaaS application that meets SaaS requirements (i.e. personalization, tenant dimensions, self-service, resource optimization, and data aggregation) is a non-trivial exercise.  The prior blog post in this SaaS series describes the requirements and constraints for SaaS applications.

Because WSO2 Carbon based middleware servers contain a tenancy framework, development teams may rapidly migrate single-tenant web applications into multi-tenant SaaS applications.  WSO2 Carbon creates a multi-tenant environment inside the middleware servers (i.e. application server, integration server, Enterprise Service Bus) and delivers unparalleled tenant density.   For more information on the cost and effort savings, read the multi-tenant, shared container PaaS white paper.

The WSO2 Carbon framework creates tenant partitions, registers tenant specific applications, provides tenant administration tools, and holds run-time tenant context.

In this blog post series, we will deploy a tenant-aware SaaS application on the WSO2 Application Server 5.1, illustrate how to acquire the Carbon Context object, and demonstrate multi-tenancy in action.  The WSO2 Application Server is based on Apache Tomcat, and extends Tomcat with enterprise security, logging, management, clustering, and multi-tenancy; turning the open source Apache Tomcat project into Enterprise, Cloud-Native Tomcat++

 

 Step 1 – Deploy Carbon and Acquire Carbon Context

The SaaS application demonstrates tenant-specific framework objects, illustrates tenancy isolation, and reviews the Java Tenancy API within WSO2 Carbon.   The application code is available from GitHub at https://github.com/karux/CarbonSaaSTest.git

The Carbon Context object holds registry, cache, queue, user realm, and role based access control (RBAC) information for each tenant run-time context. Each SaaS application can use a Carbon platform API to access context details and personalize the application experience.

 

This blog tutorial and example code demonstrates the following getting started concepts and steps:

  • Getting Started #1 – Defining a Tenancy Dimension Model
    • Step 0: Deploy the WSO2 Application Server and start server
    • Step 1:  Log into the Carbon administration console as the super-administrator
  • Getting Started #2 – Provisioning SaaS Applications
    • Step 0: Compile the CarbonSaaSTest Application
    • Step 1: Provision a Global Tenant Scope SaaS Application
  • Getting Started #3 – Acquire Tenant Context

Continue reading

Building Multi-tenant SaaS Applications

Multi-tenant SaaS applications deliver a personalized client experience while maximizing performance and efficiency.   Many teams are challenged by the specialized knowledge required to create a SaaS application on a legacy Java platform.  Creating SaaS applications requires detailed knowledge of multi-tenancy, contextual personalization, declarative programming, and infrastructure scaling.  The WSO2 Carbon platform contains unique Cloud-Native frameworks that decrease development challenges when building multi-tenant SaaS applications.

Continue reading

Enterprise Private PaaS Adoption and Differentiation

The secret is starting to leak out from multiple sources; Private PaaS adoption by enterprise end-user organizations is off to a slow start in 2012-2013.  Application development teams are missing an opportunity to accelerate their agility and operate at the speed of Now.  As enterprise teams evaluate Private PaaS alternatives and PaaS architecture, they must carefully identify cloud benefits, cloud characteristics, cloud-native platform options, and cloud adoption strategies.

Continue reading

Stratos Cloud Native PaaS Reloaded

WSO2 Stratos 2.0 reloads the definition of Cloud Native PaaS.   With Stratos 2.0, IT teams can:

  1. Move all their applications to the Cloud by plugging non-Cloud-aware servers and frameworks onto a PaaS Cloud-enablement framework. The fully extensible cartridge model allows new services, languages and frameworks, and runtime containers to be plugged in to the PaaS framework.
  2. Achieve Cloud scale for PHP applications, MySQL databases, and Tomcat hosted web applications.
  3. Deliver a single PaaS deployment over multiple IaaS environment (hybrid cloud).  WSO2 Stratos supports popular IaaS providers (vmWare, EC2, OpenStack, CloudStack, Rackspace, Eucalyptus) via the Apache jclouds project and Puppet based deployers.
  4. Improve TCO by lowering and optimizing run-time cost by moving applications to VM-based IaaS or choosing a lightweight Linux Container (LXC) deployment model that optimizes resource consumption and minimizes application infrastructure footprint.

 

Additionally,  the Stratos bits have been officially accepted as an Apache incubator project.

Cloud Native Paas Recommended Reading

Cloud Native PaaS is for Real – Available Today

 

Cloud-aware applications and PaaS architecture

Apache Stratos Brings Cloud Native PaaS to Apache

PaaS Outlook for 2013

 

 

 

 

Apache Stratos brings Cloud-Native PaaS to Apache

WSO2 has proposed the Apache Stratos project at the Apache Foundation.

Apache Foundation

Apache Stratos will be a polyglot PaaS framework, providing developers a cloud-native environment for developing, testing, and running scalable applications.  With Apache Stratos, IT providers will gain high utilization rates, automated resource management, and platform-wide insight including monitoring and billing.

Apache is the obvious choice for a project that already embodies Apache values and is driven by developers who are committers on many other Apache projects.  By donating the project to Apache, WSO2 desires to attract open community members from the following constituencies:

  • Organizations adopting Private PaaS deployment within an enterprise and accelerating enterprise application deployment.
  • PaaS providers relying on a PaaS framework to build a PaaS that is customized to their particular vertical industry, ecosystem, or internal development processes.
  • SaaS providers requiring a widely-deployed and supported elastic, multi-tenant Cloud-native platform.
  • ISPs offering hosted application services with higher resource utilization capabilities than provided by IaaS layers.
  • IaaS vendors providing higher-level PaaS services to their customers.
  • Analytics, data, integration, and application server vendors adding cloud capabilities to their products through Stratos Cartridges.

The proposed committer list includes individuals from SUSE, Citrix, NASA Jet Propulsion Lab (JPL), Sungard, and EngineYard.   Join the Apache Stratos community, participate in extending the 100% Open Source PaaS framework, and create a Cloud-Native fabric.

Apache Stratos

Figure 1.0: Apache Stratos Architecture

Recommended Reading

Apache Stratos Proposal

WSO2 Stratos Product Page

 

 

 

Apache Foundation

Cloud Native Private PaaS is for real – Available Today!

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.

Cloud Native Private PaaS

 

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

 

 

Bridge IaaS and PaaS

Bridge IaaS and PaaS to more efficiently and flexibly tackle the challenges of the modern connected enterprise.

As enterprises deploy private IaaS clouds into production, they are reevaluating their future application delivery models. SUSE and WSO2 believe that private PaaS will leverage the automation and scalability of Private IaaS solutions, such as OpenStack-based SUSE Cloud, and deliver secure, standardized development environments that will make migrating to an agile, service oriented delivery model possible.

View the Bridging IaaS with PaaS webinar presentation, and

Continue reading