We recently shared with you the results of our customer survey in which we asked our customer base what motivated them to DevOps adoption. What we found was that in more than half the cases, business put pressure on IT to evolve and address a specific business challenge. Those challenges varied from customer-driven pressures to deadlines like an upcoming data center lease expiring.
With KubeCon and CloudNativeCon in Copenhagen this week, we saw several container-related news announcements--from management to deployment and adoption to monitoring. As more and more organizations look to adopt containers for greater development efficiency and faster application deployment as part of a larger DevOps or IT modernization initiative, the hype and tools surrounding the ecosystem continue to grow. This week was certainly no exception.
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.
In a constantly-changing industry, standing still is not an option -- for your business or your career. And the same is true for the Flux7 blog, where we aim to provide you with valuable content that builds your personal knowledge and transforms your business. It is in this vein that we launch today the first of what we intend to be a regular series of DevOps news blogs, featuring highlights from the week that help keep you in the know, and driving your IT modernization forward.
Many developers steeped in the world of agile startups view continuous delivery (CD) pipelines as an accepted standard requirement for software development. Yet many companies, particularly large enterprises with traditional infrastructure, still struggle to make this approach a standard part of their development process. Whether you are an enterprise looking to make CD pipelines a standard project element to increase agility and speed time to market, or if you are looking to simply implement code delivery pipeline best practices, Flux7 CEO, Dr. Aater Suleman, has written a paper that illustrates how to deliver business value through DevOps-based automation that grows developer output and strategic contributions. Download it here or read on for highlights from his piece.
Today we’d like to share the story of how the DevOps team at Flux7 worked with a Fortune enterprise customer to help them automate their AWS VPC creation, which reduced several days of manual, repetitive tasks into a simple user interface, concluding with a single click. Saving this firm days of manpower has meant that these resources can now be used for more strategic, business-impacting activities. Read on as we share a business view into this AWS case study.
Building a continuous integration and continuous delivery pipeline is a goal of many enterprises as they look to increase their agility and speed time to market. More to the point, as part of a healthy DevOps environment, CI/CD pipelines deliver business value through automation that grows developer output and strategic contributions. For AWS-based DevOps environments, many enterprises look to AWS CodePipeline to help facilitate their CI/CD as it integrates easily with other AWS services -- and a broad set of ecosystem tools -- and provides a consistent set of quality checks for code.
According to eMarketer, ecommerce in 2017 increased 23%, continuing to surpass traditional retail growth rates; total retail sales -- including ecommerce gains -- were 5.8% in 2017. Yet, as we look into a competitive retail landscape for 2018, and begin to field calls from retailers looking to parlay 2017 gains into 2018 advantages, one discussion point is often around what role AWS best practices can play in ecommerce insurance. That is, through the process of digital transformation, building in consistency and availability for retail customers regardless of the channel they choose.
Moving to the cloud allows you to manage infrastructure in new and incredibly powerful ways. Unlike traditional, manually managed infrastructure, the cloud empowers Infrastructure as Code(IaC) in which entire infrastructures can be implemented and managed with automation. While IaC offers real benefits in ensuring environmental consistency, growing the pace of innovation, and increasing overall quality, to effectively manage your code, it is important to codify and version it, which is best done through a source code repository. Yet, that is often easier said than done with teams in agile DevOps environments needing to effectively navigate, retrieve and collaborate on code. At Flux7, we have implemented several DevOps best practices for organizing source code repositories which makes this collaboration easier, in turn saving time and potential rework.