When it comes to defining and deploying enterprise cloud applications, traditionally, there has been a healthy tension between the developers, architects, and IT Operations. This is largely due to the needs and success measures for these stakeholders being different and not fully aligned with the overall goals of the enterprise.
Developers want to focus on code and develop, test, and deploy their applications faster with unbridled freedom. Key requirements include:
- An agile development environment that can be created and torn down at will, on demand.
- Self-service of infrastructure components, such as servers, and services such as runtimes, databases, load balancers, scripts, etc.
- Ability to replicate QA, production, or customer environment effortlessly
In general, the QA requirements are similar to those of developers, except with a focus on building a QA setup that is identical to a production environment in terms of scale, performance, security, and other capabilities.
The requirements from architects’ perspective are different but equally important to be addressed.
- Developing and driving standards and best practices
- Integrating new technology and rapidly developing blueprint for application innovation
- Avoiding repetitive, tedious tasks
Meanwhile, the IT Operations team is responsible to fulfill the requests from developers, QA, and architects.
- Ensuring service level agreements (SLAs) are met for the services consumed
- Balancing tactical needs with longer term projects
- Positioning IT as an enabler of innovation and eliminating bureaucracy while retaining control to ensure compliance and governance.
Traditional approaches to addressing these problems have yielded sub-optimal, partial, and siloed solutions tightly coupled to the underlying cloud infrastructure. Consequently, collaboration is inefficient and lower productivity translates into slower innovation of new applications for the enterprise.
ElasticBox dramatically changes the game by fortifying the synergies between the stakeholders and streamlining the develop-test-deploy cycle in a boundary-less manner. Application definition can be completely separated from the details of the underlying cloud infrastructure.
Using ElasticBox, each of the personas can flexibly integrate their knowledge and expertise into the application life cycle. Reusable software components, called Boxes, can be created which include run times, web servers, and middleware. The library of templates so developed can be shared as a self-service catalog throughout the organization. Access based policies for resource allocation and scaling can be assigned based on users and groups to ensure governance.
This is the power of true win/win/win collaboration between developers, architects, and IT Operations. We simply call it the 1+1+1=5 effect.
What is the level of collaboration in your organization between the developers/QA, architects, and IT Operations? Why not build an application lifecycle process that celebrates the healthy tension between these personas while empowering each stakeholder to unleash their potential?
Self-service and IT governance can harmoniously coexist. Who said you cannot have the cake and eat it too!