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.
We recently had the opportunity to work with a pharmaceutical company that is breaking new ground when it comes to treatments for life-threatening ailments like cancer. Seeking to innovate across the organization -- from R&D to IT -- this company reached out to the DevOps team at Flux7 to help it migrate its Cloudera Hadoop-based analytics systems to AWS. Specifically, the vision was to take all of its diverse data sets to the cloud, establishing a highly available and secure environment where the firm could conduct data modeling and data analysis while protecting sensitive data and ensuring GxP and HIPAA compliance. Read on for the full AWS case study.
We are excited to announce that one of our customers, TechnipFMC, a world leader in project management, engineering, and construction for the energy industry, has been featured as an AWS case study. TechnipFMC had a specific challenge they were looking for help with when they called the AWS consultants at Flux7. Specifically, they were looking to ensure security and compliance for its global sites and the perimeter networks that support its client-facing applications.
As an Austin, TX based DevOps consulting firm, we work often with organizations in the energy space, empowering them to directly address business drivers and see their ideas come to life with the application of modern technology. So it was in this vein, that we were approached by a publicly traded, global solar company who wanted to use a cloud migration as an opportunity to overhaul its business processes. (You can read the full case study here.) Specifically, they were looking to use the opportunity to grow developer agility, gain global access for their workers and to save on capital expenses while maintaining compliance and building-in standardization.
We have been working closely with a customer who is undergoing a business transformation. As a multimedia equipment manufacturer, the organization has a loyal following of its high quality devices. However, like many companies facing the convergence of markets and new customer demands, the company has embarked on a metamorphosis. Traditionally very focused on hardware, their software was largely ignored even though it offered customers real value. Part of the company’s transformation was a move to treat their software like a full-fledged offering, rather than a free supplement. An upcoming product release marked the first (and biggest steps), in cementing this change in company direction.
There are many reasons an organization might choose Amazon Aurora over the Amazon Relational Database Service (Amazon RDS). Superior performance, greater scalability, and the ability to restart without losing cache are just a few. However, for those organizations who are already running an important application or Website on top of the RDS managed service, it can be a challenge to migrate from it to Aurora, despite the latter’s obvious benefits. After all, you can’t just take down a service that customers expect access to 24x7.