Why IaaS and PaaS Defy the ‘First-Things-First’ Mentality 

By Atos Apprenda Support


As enterprise organizations adopt Platform as a Service (PaaS) into their software delivery roadmap, they are faced with perception challenges concerning enterprise PaaS. Very often, organizations have a bottom-up view of their technology stack (“stack” being the trouble word in that phrase). While this is a valid way to organize thoughts around a technology portfolio, this visual implies a “first-things-first” mentality when it comes to IaaS versus PaaS and which layer receives transformational attention before the other.

Customers often pump the brakes on PaaS while they get their infrastructure in order. Customers will say, “We need to get our IaaS story straight before we can put a PaaS on top of it.”

While this is certainly a cautious strategy, it’s a missed opportunity to mitigate risk while transitioning to an “as-a-service” environment. Maintaining such a tight coupling between the infrastructure and application layers complicates the execution of roadmap goals while increasing risk due to existing dependencies.

Organizations need to provide developers with solutions in order to deliver software as quickly as possible, while enabling operators the ability to modify the underlying infrastructure without impact to software (i.e. value) delivery.

Apprenda’s approach to enterprise PaaS involves leveraging your existing and future assets while also providing the speed-to-value of PaaS to both developers and IT teams on day one. For example, by abstracting the application layer of the stack using a platform, developers can enjoy seamless deployment on existing assets while operators modernize the infrastructure “under the hood” without application disruption.

The Apprenda platform relies solely on operating system instances in order to run and does not force the business into determining an IaaS strategy prior to implementing and rolling out the PaaS. Apprenda’s goal is to abstract both developers and applications from the underlying infrastructure while allowing operators to work freely with no impact to enterprise applications.

Operators and infrastructure owners can leverage a variety of infrastructure assets (bare metal or virtualized) while utilizing the Apprenda platform. As your IaaS strategy takes shape and new servers become available, workloads can be shifted from the existing infrastructure to the new IaaS-deployed one.

The application developers are not impacted, as their deployment methodology doesn’t change. Application users are not impacted as the applications continue to run uninterrupted while being moved to different infrastructure assets. Uptime is preserved while operators modify their infrastructure with zero downtime.

Developers enjoy consistent deployments of legacy applications and they can deliver non-functional (refactoring to cloud-native, 12-factor patterns) and functional (UI changes, new features) changes rapidly without holding up the operations team from achieving their IaaS abstraction goals. The goals set by the developer and operator teams need not interfere with each other. However, they can both be served by initially utilizing a PaaS to decouple and abstract the application from the underlying infrastructure and vice-versa.

Wrap Up

Apprenda is excited to assist enterprise customers decouple their applications and infrastructure and to accelerate their roadmap execution through abstraction. Customers no longer have to put abstraction on hold to reach enterprise goals. We’re here to help and happy to answer your questions.


Atos Apprenda Support