Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

DevOps Use Cases

DZone's Guide to

DevOps Use Cases

Financial services and insurance lead twelve other verticals in using DevOps to problem-solve and improve performance.

· DevOps Zone ·
Free Resource

Learn how integrating security into DevOps to deliver "DevSecOps" requires changing mindsets, processes and technology.

To understand the current and future state of DevOps, we spoke to 40 IT executives from 37 organizations. We asked them, "What are a couple of real-world problems being solved with DevOps by your company or clients?"

While DevOps can improve any organization's performance, financial services and insurance were the dominant industries for use cases shared by our contributors. Here’s what they said:

Financial Services

  • Financial services are about enabling massive operations. We do load balancing for organizations. Load balancing ensures the quality of a service. Dedicated environment to ensure quality. Moving to microservices infrastructure as distributed in multi-cloud.
  • A Swiss bank went from a new virtual machine to load balancers in six weeks. The bank brought in a console as a service registry and was able to bring conversion tie from six weeks to five seconds.
  • Financial services, a large bank creates dozens of new APIs and digital services in less than five months. Would have taken 18 months. Embraced DevOps, microservices, agile development and are seeing the results by moving much more quickly than ever imaged. Another is financial services able to integrate legacy apps on a mainframe with an Amazon Function Cloud and automate the process of creating and deploying the APIs. There's no need to provision ahead of time and they can react to spikes in demand to increase digital presence and channels. If there's a spike in demand scalability is amazing. Don’t pay for it if don’t use it. They've now 2,000 APIs in four months with function-based APIs.
  • A financial services company is preventing things before they even happen. Autonomous remediation. The customer took data and applied AI/ML ops. Look at data from last three months. See where you had an outage. When they do this, customers apply AI/ML to see what’s happening and are then able to prevent it from happening. Remediate problems automatically.
  • One of the largest banks in the US needed to modernize their delivery cycle in order to set up a new online system. They overhauled their platform and added Jenkins for CI, which increased deployments and speed, but it lacked the version controls they needed for compliance. We enabled them to keep using Jenkins and the other technologies on their platform, like Docker, Kubernetes, and OpenShift, but let them control which version is running in which environment. 
  • Key Bank has gone from a three-month deployment interval to a one-week deployment interval. They went back to developers and told them they owned what’s in the container while ops owned the container itself. Running is what matters most in what you do. It adds no business value until it’s in production. DevOps philosophies were established up front. 
  • The financial market is a super-dynamic environment, with constant changes being driven from different perspectives around the globe, such as new financial regulations and reporting requirements. As a technology provider in this industry, our ability to provide timely solutions to our clients is critical. Our early adoption of a DevOps practice and our ongoing effort to constantly keep improving our build and deployment processes and workflow is definitely a key pillar that makes this possible. With our DevOps practice, we are also able to reduce the cost of keeping our production deployment footprint up-to-date for OS and infrastructure upgrades.

Insurance

  • Colonial Life is now modernizing the rest of their business since they’ve seen they could improve their most complex application.
  • We have a customer—a large insurance company—that wanted to automate their release processes to get improvements to customers faster. They had a lot of automation tools, which created a lot of dependencies. They were also dealing with how to stay compliant across all their different pipelines. They used a single release orchestration template which allowed them to standardize on one pipeline for a dozen technologies. 
  • A large insurance group in France implements continuous delivery and reduces the time it takes to put changes into the product by 90 percent, reducing weekend work by 50 percent.
  • A major global insurer reduces annual costs from $3 million to $120,000 per test environment, reducing environment provisioning time from six weeks to two hours.

Others

  • 1) The early failure-to-success of Twitter initially rolled out with Ruby on Rails and had many outages due to scale. Started with an easy to use developer environment but not scalable. Hired experienced talent to operationalize scalability. 2) Pokémon Go was a wild overnight success, blew past deployment specs and were able to take advantage of the cloud and their deployment tools. Used K8s. 3) Fortnite has done an excellent job of taking it one step further, don’t blame, write up detailed descriptions of their failure and publish them seek input and comments to help solve problems. Writing up a post-mortem to share information about problems and solutions. Blaming people is not as useful as rewarding for identifying the problem and reporting.
  • Customers in finance, oil, and gas, pharmaceuticals, retail are using DevOps. Oil and gas are using multi-cloud at the edge.
  • A private data center group becomes more agile. Six weeks times 700 applications – it's the best technology deployed in seven years.
  • Large purveyor of coffee shops with a global presence wants to increase revenue by having a more direct digital experience with customers – app, offers, pay. Storing a lot of information securely is important. Expand use into different geographies, provide security backend to protect data. Able to move forward with confidence to invest more in the app.
  • 150-year-old company people running systems are leaving. A decade before hardware gets replaced. Get control and visibility into processes of compiling and shipping mainframe code. We don’t retire technologies. We don’t tear down buildings even though they don’t have the latest technology. Learn from conferences, training, and education, some is self-taught. DevOps dojos to work with the support group to teach by doing going through a two-week scrum to identify what’s impeding velocity. 1000 product teams have to figure out how to educate. We train the trainer.
  • A major airline was able to increase release velocity by 100 percent, providing major customer improvements with their online reservation and check-in systems. 
  • Our clients release more often, and they release fearlessly (our slogan is #DeployFriday). Customers like Arsenal FC are no longer on “code freeze” during critical periods. They can innovate for their fans and push code on game days. They also worry less about scale, with the ability to adjust resources dynamically through code.

Here's who shared their insights with us:




Learn how enterprises are using tools to automate security in their DevOps toolchain with these DevSecOps Reference Architectures.

Topics:
devops ,fintech ,insurance ,performance ,financial services

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}