As part of our ongoing blog series on DevOps adoption, we’ve touched on the topic of migrating systems to the cloud as it helps codify DevOps best practices via an ecosystem of tools steeped in IT process automation. Today we’ll dive a little deeper into the topic of cloud migration, exploring in greater depth the topics of replatforming, refactoring, how the two compare, and when you might favor one approach over the other.
As part of our ongoing blog series on DevOps adoption motivators and best practices, we recently shared Seven Lessons for a Successful DevOps Pilot in which we touched on the criticality of choosing the right team to staff your DevOps pilot. In today’s blog, we will dive deeper into our recommendations for the ideal team size, composition, and the roles each team member should play.
The cloud is changing the way we talk and think about IT and the leading cloud proviers are consistently transforming cloud computing to bring even greater depth and maturity of services to IT organizations in their pursuit of IT modernization. Each year Gartner takes a step back from this cycle to look at the cloud infrastructure market, helping organizations who are both new and existing cloud users analyze the state of the market and vendors therein.
This article originally appeared on Forbes.
With more and more infrastructure and applications moving to the cloud in support of digital transformation, one of the decisions enterprises must confront is the best approach to cloud migration for long-term success. While some favor a lift and shift model, others come down on the side of replatforming or even a refactoring approach. However, there is no single path to success. And, indeed, a hybrid approach is often the ideal answer.
In our last article we discussed how to smartly select a pilot project to prove out the benefits of a DevOps organization. As you begin to put your DevOps adoption plan in place, one thing that should be included -- regardless of the project chosen -- is a Landing Zone. As you transition from a traditional Development - IT Operations framework, the Landing Zone is important as it provides needed efficiency, standardization, and governance.
For organizations facing competitive pressures that drive them to DevOps adoption, it is critical that they correctly choose, scope and evangelize a ‘right-sized’ pilot project to start their IT transformation. As sherpas for many organizations who travel this path, at Flux7 we’ve learned many DevOps best practices -- as well as things to avoid along the way. As you look to create a successful DevOps pilot with sustaining impact, please join us as we share seven important lessons learned.
At Flux7, we ask every customer their motivation for DevOps adoption and a potential move to the cloud. Curious if the pundits’ thoughts on the topic resonated with our customers’ experience, we recently analyzed the answer to this question across our customer base, which consists of Fortune enterprises as well as mid-enterprises in a wide variety of industries. What we found was fascinating and informative. The majority of organizations were motivated to DevOps adoption as a result of pressure on the business from customers, competitors or other outside forces.
When it comes to the most popular tools and technologies for IT Modernization and cloud computing, this week’s news rules them all. As you’ll see, this week saw the announcement of Linux Ubuntu 18.04, by far the most popular cloud OS, according to research by The Cloud Market. In fact, it’s so popular that it is chosen at a rate of almost 2:1 of the next four OSs combined. AWS also continued to prove its rank as the leading cloud provider as it released its Q1 earnings.
As an AWS Premier Consulting Partner, we are often asked about using the Kubernetes container management system within AWS. While Google created Kubernetes (K8s), Google’s Cloud Platform is generally seen as a better fit for running K8s clusters. However, until the recent re:Invent announcement of EKS, KOPS, the Kubernetes project for managing production-grade K8s clusters, was the best tool to deploy and manage K8s clusters in AWS. Which brings us to the topic of today’s blog, a customer story of how we used KOPS to run AWS-based K8s clusters. Stay tuned for the second part of today’s AWS case study in which we discuss the details of doing so with Ubuntu CIS benchmark images.
Any journey begins with a first step and that’s exactly the approach this financial service firm had in mind when they asked the AWS experts at Flux7 to come in and help. Specifically, the IT team wanted to start with a small project that would set them up for future success. Using Flux7’s Enterprise DevOps Framework, we were able to help them focus on an achievable first step, the migration of their Atlassian stack to AWS, with a longer term roadmap. Read on as we share this AWS case study.