How Financial Services Are Profiting From DevOps in a Big Way
Financial services organizations have traditionally been slow-moving, but DevOps is starting to make real headway in modernizing their IT ecosystems.
Join the DZone community and get the full member experience.Join For Free
the amazons and googles of the world are humming along a mile a minute when it comes to innovating on modern software delivery practices and deploying software updates rapidly. these web-first, unicorn companies facilitate business at incredible speeds and with a level of agility that earns their customers’ love and loyalty. they have created a new standard and set high expectations for service that can be difficult for other industries to match, particularly ones in highly regulated businesses such as financial services.
devops is changing all that.
financial services organizations face great challenges in meeting the new standards set by the unicorns. many did not start online, and they’re busy modernizing back-end processes and systems to support today’s digital age. in addition to legacy systems and code, they face concerns around mitigating risk for better security, complying with regulations, and meeting governance requirements, all of which make software innovation a complex and slow process. or so you would think.
over the last few years, however, the financial services industry has not only caught up, but is leading the change when it comes to speeding up innovation and adopting modern software delivery practices such as agile, continuous delivery (cd), and devops. executives in this conservative sector see devops as a way to roll out value to the market faster, more efficiently, and more safely. devops enables financial services to increase the cadence and quality of application releases while also addressing governance, risk, security, and compliance strategies.
security and compliance objections overruled
security and compliance are top concerns in financial services and have often been the first arguments against modernizing legacy software development and delivery practices—they are the wet towel thrown on devops efforts. initially, devops practices were viewed as a risk to security, and the increased velocity of software releases it enables was seen as a threat to governance, security, and regulatory controls.
despite the initial pushback, however, enterprises that took the devops plunge have consistently demonstrated that these practices actually mitigate potential security problems and help organizations discover issues and address threats more quickly. this has led to the embrace of automation practices as a security blanket that enables and enforces security, compliance, and audit requirements. these financial services organizations now see devops as a resource for security efforts, rather than as a threat.
breaking down the walls of the distributed enterprise
for many large financial services organizations, each of the four basic stages of the software delivery pipeline — build, test, deploy, and release — consists of hundreds of different processes that encompass thousands of tasks and sometimes millions of jobs executed by hundreds of people. to make things even more challenging, these people, processes, and tool sets often exist in geographically distributed silos.
within these silos, people may be adept at understanding and improving their piece of the puzzle, but there’s no end-to-end visibility from an organizational perspective, and there’s no way to orchestrate the entire pathway that code takes from build to test to production. this leads to fragmented processes, manual handoffs, delays, errors, and a lack of governance.
because development teams and it operations are often geographically distributed in these large enterprises, it is imperative to enable shared control and visibility into the different infrastructures, tool chains, and processes. this is because optimizing the software delivery process should not be attacked as a disparate set of problems but seen as using a system-level approach, much as car manufacturers apply lean manufacturing principles throughout their production lines.
devops adoption and implementation are spreading rapidly in financial services due to the value that this systems-level, global approach enables. it does so by scaling modern it processes across the entire enterprise to enable a robust, end-to-end pathway to production. breaking down functional silos and removing friction between teams by orchestrating all aspects of the software delivery pipeline in order to create predictable, repeatable processes that can run frequently and with less human intervention alleviate many of the challenges distributed organizations face. to achieve consistency in the release of software, organizations promote visibility and a “learn fast, fail fast” culture, which helps optimize governance.
improved visibility and control
another essential to improving developer productivity, product quality, and resource utilization, as well as to enable enterprise-scale and cross-project visibility and management in financial services, is automating the processes throughout the software delivery pipeline. “automate all the things” is a key motto for any devops or cd initiative, and it’s becoming a requirement for achieving higher product quality, ensuring compliance, and enabling speed and scalability.
devops provides enterprises with an effective approach to eliminate risk from software releases and support the ever-growing demand for more frequent application updates. by automating the entire end-to-end pipeline and managing all release processes in one centralized platform, these organizations gain visibility into the progress of all releases and devops processes and ensure that they can control, govern, and optimize their delivery pipelines even as they grow.
from a systems-level perspective, leveraging automation across the enterprise facilitates the standardization and consolidation of all tools, processes, and environments across the organization. this often requires a centralized, shared devops release automation platform to allow for the seamless tie-in and orchestration of all the disparate set of tools and processes involved in software delivery. this then enables reusability across teams and the shortening of cycle times and cost reductions. it reduces the risk of releasing software by having predictable processes in place to provide consistent security checks, necessary approval gates, and controls where needed.
leading a cultural change
as a philosophy, devops focuses on creating a culture and an environment where development, quality assurance, operations, the business, and other stakeholders work in collaboration toward a shared goal.
while optimizing the tools and technology to scale devops adoption, automating the lifecycle, and embedding security practices throughout are important steps, they are only half the battle. devops is a mindset, and any cultural shift takes time. this transition will not happen in a day, but even the heavily regulated financial services industry is on the devops bandwagon, leading the change not only from a technology standpoint, but also from a cultural one. financial services organizations finally have what they need to fully harness the benefits of devops, modernize their business, and keep pace with the unicorns.
join me at devops enterprise summit london on june 30-july 1, where he will be talking more about cultural change and devops as part of my presentation, “ the yin and yang of devops transformation .”
Opinions expressed by DZone contributors are their own.