Blog

9 Emerging Operations Gaps That Will Empower Your Cloud Strategy – Part 1

By Atos Apprenda Support

Hope Is Not a Strategy

In sales, politics, and Google’s SRE book (which is now available online for free), it’s been heard that hope isn’t a viable strategy by itself; it can, however, lead to a strategy for success, especially when utilizing cloud technologies. Carrying momentum from 2016, these technologies are at a turning point for enterprise operations and are now helping evolve ideas from hopeful claims of a Solutions Architect into business strategies financed by C-level execs. These projects are the basis of several successful strategies in the last year, focusing on modernizing the Production technology stack.

From migrating apps to a PaaS, to implementing new CI/CD workflows, to improving the SDLC through cloud readiness assessments, these modernization strategies will ramp-up globally as we get further into 2017. Are you ready to modernize?

From Ideas to Solutions

Consider these statements, often heard during strategic roadmap discussions:

  • We hope by moving our application portfolio to a PaaS, we will significantly increase the speed of development and deployment to Production.
  • Our IT team hopes introducing IaaS to our stack will significantly reduce operations’ cost of maintaining on-premise data centers.
  • The developers hope that by implementing a Big Data solution, we will improve time spent finding data by upwards of 60%, and thereby increase the security and availability of our business analytics.

Hope is a feeling of trust, and it is also the basis of every successful strategy. This is especially true in software-powered industries, where a growing menu of options are available to run the business and the risk of failure is increasingly high. Decision makers must choose a technology stack that will:

  • Take the business to the next level, and rise above the competition
  • Maintain availability and reliability for the next 10 years
  • Increase operations efficiency
  • Mitigate problems that are consuming limited operations resources

Taking all of this into account, a leader can make a strategic decision with hopes to move the business forward and hand the project off to a trusted team. It is now up to that team to turn once hopeful statements into real solutions.

The Cycle of Evolution

Let’s introduce DevOps into what we’ll call the Cloud Migration Project. A trusted team now spends months executing a solution that will:

  • Refactor and/or containerize most of the business application stack
  • Implement new CI/CD workflows from development to Production
  • Migrate most of the Production systems to cloud-based architectures

This is done all while utilizing IaaS, PaaS, or anything-as-a-service and, hopefully, it ends with success. Unfortunately, though, these long-term greenfield initiatives may never see success.

This is because the cycle of evolution is outpacing the implementation speed of cloud-native solutions. So before the team can properly roll out today’s solution, tomorrow’s new shiny object becomes a distraction. In our example, the Cloud Migration Project won’t nearly be complete when architects and engineers start thinking about the Better Cloud Migration Project.

How can you mitigate failure of a project like this? Deliver a viable solution faster, and prove the benefits. To start, take a look at your operations technology stack. Consider gaps in the following areas:

  1. Monitoring
  2. Dashboards
  3. Alerting
  4. Logging
  5. Load Balancing
  6. Concurrent Pipelines
  7. Capacity Planning
  8. Resource Throttling
  9. Troubleshooting

In part 2 of this post, we will cover a brief gap-assessment in these 9 areas. We will also exemplify how you can utilize existing cloud-native technologies to close these gaps today with a Kubernetes platform. Furthermore, part 2 will describe how you can use this platform to empower your cloud strategy, and encourage the business to migrate more applications.

Atos Apprenda Support