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.
As we look back on 2017, it was a year full of transition. And, one in which many organizations began -- or continued to -- invest in their transition to cloud computing. According to research by IDC, public cloud services spending was expected to reach $128 billion in 2017, a 25% increase over 2016. Much of this was driven, according to polling by TechTarget, by senior IT executives looking to increase innovation, and reap cost efficiencies from the cloud. Indeed, those among this audience who grew their 2017 budgets, 64% said they would increase their budget for cloud services, including computing, storage and applications -- more than any other area TechTarget asked about.
As 2017 draws to an end, we are taking a moment to look back on the year that was and share some of the most popular insights from the Flux7 DevOps blog. Industry-wide, interest in DevOps soared in 2017, and that was reflected in our readers’ blog choices as well. More and more companies are undergoing digital transformation and embracing the idea that technology is core to their business and provides them with an advantage in the marketplace. These companies are increasingly insourcing their technology and adopting a DevOps methodology as a way to become more agile and speed their time-to-market, proving the adage that “every company is a technology company.” Helping these organizations on the path to DevOps success were several very popular blogs.
In the middle ages Byzantine emperors and European monarchs issued decrees with a golden seal that was testament to the origin of the decree. Fast forward to today and we can see how the idea of a golden seal -- or golden copy-- is used in technology to express that something is the official or master version. Taking the idea of a golden copy one step further, today we will discuss the concept of the golden Amazon Machine Image (AMI), its role in supporting a successful DevOps model, and how it can generate greater agility and stability.
We embrace the transformative opportunities DevOps provides and when coupled with agile practices, enables us and our customers to move quickly and drive innovation. One of the ways our team embodies agility is through remote service delivery. While this practice runs counter to how consultants have traditionally worked, we are often asked about the advantages of remote delivery and thought we’d share today the upsides of this approach and how it supports the agile DevOps model.