Underscoring a rapid shift in DevOps automation and IT Modernization, Cisco Systems released findings this week of a new survey in which IT Leaders reported that within two years more than two-thirds expect their approach to become either predictive (33%) or preemptive (33%). Indeed, 42% of respondents said they
It is spring and that means it’s conference season. Two events this week that caught our attention were the ServiceNow Knowledge Conference and Red Hat Summit, both of which, like clockwork, had several DevOps news announcements worth sharing.
We recently had the opportunity to work with a popular quick serve restaurant (QSR) who reached out asking if Flux7 could help speed its developer outcomes for faster time to market. For this global enterprise, the goal manifested itself in a project where Flux7 helped the QSR create one-click automated installations of various products, including Amazon Redshift, through AWS Service Catalog which helped make development more efficient and productive-- through automation that minimized process overhead. Today we’d like to share the story of this AWS case study project.
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.
We are excited to announce today that we have achieved our third AWS Service Delivery Partner status, this time for AWS Service Catalog. (You can view the news release here.) This is an important recognition for the Flux7 team of DevOps consultants as the AWS Service Delivery Program only highlights AWS Consulting Partners who have a track record of success delivering verified customer solutions for specific Amazon Web Services (AWS) products.
We recently worked with a Fortune 500 manufacturer of heavy equipment that is focused on quality, productivity, and effectively connecting its customers with data-driven insights via technology. As an international, publicly traded organization, it is also careful about managing security, risk and compliance. So, when this manufacturer asked if we could set up an audit and notification system, we were happy to roll up our sleeves and begin work. (You can read here the full case study of this Fortune 100 customer.)
While microservices benefit a variety of organizations on multiple fronts, (for a deeper discussion on this, please check out our blog, “Microservices Trend as IT Competes on their Respective Strengths”) today we are examining how one startup used a microservice architecture to give developers greater agility and add automation to gain a competitive advantage in its industry.
How Flux7 Helped Increase Developer Productivity with AWS Service Catalog
At Flux7, we are expert at helping healthcare organizations gain a competitive advantage in the market through IT modernization projects that amplify their inherent business strengths. So when were approached by this healthcare organization who sees technology as a competitive advantage, we were quite excited to dive in.
At the re:Invent conference in Las Vegas last week, we had the opportunity to present a Flux7-powered case study of a successful containerized migration to AWS. As part of the session, “Getting Technically Inspired by Container Powered Migrations”, Flux7 CEO, Aater Suleman, shared Flux 7’s recent work with Rent-A-Center to perform a Hybris migration from their datacenter to AWS.
Continuous Delivery (CD) is a core facet of successful DevOps and as a result, a core Flux7 strategy for implementing DevOps-based IT modernization. At Flux7, we always view DevOps as streamlining the delivery of not just Code but also the delivery of Infrastructure (networking, firewalls, VMs), Server Configuration (software packages such as Apache or JAVA), and Security Rules (policies for AWS Config Rules or HashiCorp Vault). Among these, efficient delivery of infrastructure and configuration are both very critical for full stack agility. For our customers in AWS, our typical choice for infrastructure delivery is CloudFormation. We like AWS CloudFormation because it is native to AWS, follows a simple YAML or JSON syntax, and has deep integration with other AWS Services such as the AWS Service Catalog.
In addition to the announced AWS CloudFormation YAML support, AWS also announced cross-stack references for CloudFormation. (For Flux7 commentary on YAML support, please see our blog post earlier this week here.) As our AWS experts work daily with CloudFormation, we were very interested in this news and couldn’t wait to roll up our sleeves and take a look for ourselves.
Self-service IT is an important goal for many of our clients. They are looking for ways to increase their repeatability and speed the rate at which internal customers are serviced. Service Catalog effectively addresses each of these goals by providing automated infrastructure provisioning through easy buttons. Ops teams create these buttons and make them available to internal customers such as developers, engineers, or QA to easily request, receive and provision pre-approved infrastructure.
I had a friend ask me the other day how many meals I make at dinner time. One, I replied. But, you have kids, she stated incredulously. Yes, but I don’t run a restaurant. And neither does IT. However, IT has been treated like a restaurant for decades, with different people and departments placing their orders for specific technologies, with a dash of speedy service on the side.
Last week was AWS re:Invent 2014, the annual Amazon Web Services conference. Every year, the event brings with it the newest announcements in Amazon cloud products, services and strategies.