Large corporations around the world currently face digital business challenges. In order to remain relevant in this new norm, they have no choice but to reach new business agility standards defined by Internet-era behemoths such as Netflix, Amazon Web Services and Google.
Part of this necessary response is the rise of DevOps. In fact, Gartner recently reported that 25% of Global 2000 companies are expected to adopt DevOps by 2016. However, in order for DevOps to co-exist with legacy IT, it is important to leverage MFT infrastructure.
Is your MFT:ready for DevOps?
The Move to DevOps
In the digital age, technology is predominantly software based. Correspondingly, a key to digital success is ensuring software is agile enough to be able to constantly adjust in response to customer experience demand. For digitally native organizations, one such method is DevOps.
Until now, the time between the expression of new customer requirements and the availability of resolutions for end users was long and drawn out, involving a complex process of many steps and different teams from development to operations. Shortening that cycle in a digital present and removing such complexity, DevOps methods provide ways to ease and accelerate the collaboration between developers and operations. By relying on automation, DevOps can remove the root causes of friction between the two teams based on their unique goals. For developers, that means adapting quickly to user requirements. For operations, that often means, “if ain’t broke, don’t fix it”.
DevOps for Digital Immigrants
Organizations born in the digital age generally benefit from one platform and application supporting DevOps from inception.
That is very different from existing large corporations that are dealing with IT since the beginning of IT itself, faced with countless platforms and applications spread out on thousands of heterogeneous servers.
Here everything appears more rigid than agile.
Despite of the weight of such legacy requirements, best-in-class digital immigrants are still able to release applications rapidly, even four times a day.
The goal is achievable and is made of tools, methods and great architecture design.
MFT – DevOps Friendly
In order for larger longstanding organizations to succeed, DevOps has to work with MFT, a traditional mainstay in enterprise architecture. The good news? Comprehensive MFT solutions are DevOps friendly and can fit well with DevOps requirements. For instance, MFT solutions can establish a clear contract between applications and the transport layer, they are easy to test, to automate, and to monitor and thanks to features related to file transfer integrity, MFT is highly stable.
Ensuring your MFT is Ready for DevOps
In order for MFT to work with DevOps, organizations should look to establish:
- A map of data flow: in large IT, an individual application doesn’t mean an isolated application. Each application is part of a global value chain. When changing an application, it is important to understand how the change impacts other applications. The flow of data is the data link between two steps in business processes. Having a data repository that lists the flows and the applications and provides the characteristics of each flow is vital. This includes who was involved (persons, applications, partners), what the purpose was, and how it was measured and controlled. Automation of flow deployments: When a data flow is impacted by a change to an application, it is extremely beneficial to have the associated change to the flow definition automatically generate the configuration updates to underlying platforms. By doing so, organizations can ensure consistency between requirements and deployments and between each end point of a data flow.
- APIs: By leveraging APIs, organizations can synchronize the application promotion with the associated flow configurations.
DevOps is here. Is your MFT Ready?