One Bank’s Path for Moving Deep Legacy Infrastructure into Cloud Native Operations – InApps Technology is an article under the topic Devops Many of you are most interested in today !! Today, let’s InApps.net learn One Bank’s Path for Moving Deep Legacy Infrastructure into Cloud Native Operations – InApps Technology in today’s post !
Read more about One Bank’s Path for Moving Deep Legacy Infrastructure into Cloud Native Operations – InApps Technology at Wikipedia
KubeCon+CloudNativeCon sponsored this podcast as part of a series of interviews with Kubernetes end users. Listen to the previous stories from one server to Kubernetes, a startup’s story and the ups and downs of Box’s Kubernetes journey.
Some legacy infrastructures are certainly more difficult than others to shift into cloud native operations. Financial services, for instance, have many regulatory, compliance and data-management challenges, which are further amplified if the company has an especially large international presence.
In this edition of InApps Technology Analysts podcast, as part of InApps Technology’s recent coverage of end-use Kubernetes, Michael Lieberman, senior innovation engineer, vice president, of Tokyo-based investment services company MUFG (Mitsubishi UFJ Financial Group), discusses his company’s journey to scale-out architectures in a microservice and Kubernetes environment in the world of financial services. Alex Williams, founder and publisher of InApps Technology hosted the podcast with co-hosts Cheryl Hung, vice president of ecosystem at Cloud Native Computing Foundation (CNCF) and Dave Zolotusky, senior staff engineer at Spotify.
Listen to all TNS podcasts on Simplecast.
From the outset, MUFG’s transition to a cloud native infrastructure has involved a cultural shift in how its team members operate. The adoption of cloud native tools and technologies to help meet the international banking sector’s legal and regulatory requirements required more openness about its requirements, said Lieberman.
In the past, banks generally have kept their tools and technology choices “very close to the vest,” Lieberman explained. This can pose problems on several fronts.
There have been some “situations where tools and technologies we could use maybe are not available for use because the people who are developing them aren’t aware of our requirements or aren’t aware of our needs,” said Lieberman. “So the thing that we’re trying to do is we’re trying to be a little bit more open with discussing those requirements and discussing those needs with other vendors and the open source community at large.”
As is typically the case with a financial services firm, MUFG’s stack has consisted of a significant percentage of legacy infrastructures, including, of course, “old mainframe of stuff” with a lot of Java-written code in its stack, said Lieberman.
MUFG’s transformation to cloud native has involved the adoption of Red Hat’s OpenShift to help smooth the processes. At the same time, MUFG is exploring many different options and choices. “And with that, we’re also still exploring stuff like vanilla Kubernetes… I think we’re still fairly… early on in our journey… and we’re still evaluating a lot of the other cloud native tools and technologies.”
However, while MUFG is largely in the early stages of its shift to cloud native, Kubernetes has already been “a huge lift for us,” he said.
“One of the big things that Kubernetes has allowed us to do is to use API-development frameworks. [Kubernetes] has allowed us to…get that feedback loop to the developer quicker — where you can imagine, a mainframe is not really intended for fast change,” said Lieberman.
“So with that said, moving over to Kubernetes, we’ve been able to have it set up now where a developer can make a change to any of the hundreds of microservices we have running and we can start to run a full suite of tests against those microservices in our Dev environments.”
The Cloud Native Computing Foundation and Red Hat are sponsors of InApps Technology.
Let’s create the next big thing together!
Coming together is a beginning. Keeping together is progress. Working together is success.