Grounded in the Cloud
Showing results for 
Search instead for 
Did you mean: 

HPE Helion Stackato Evangelism: Part 4: Bank Transfers and Knowledge Transfers



large (3).jpg

Guest post by, Tim Clayton, Marketing Business Services

“We wanted an opportunity to do something different.”

In the first blogs of this series we’ve looked at a couple of very different solutions. The NDC Adaptor showed us some challenges of bringing a solution to the cloud and how developers are learning to solve problems. The OCCO solution outlined how a new idea can be built from scratch in the cloud. This blog, about taking the HPE Card Authorization Solution into the cloud, is about both these things—and more. It is about moving the existing into the cloud but building from scratch. And it is a story of passing on knowledge from one to another. This is a tale about taking control of a project, with the express intention of giving it up later on.

I’m speaking to Vikranth MohanRao about his team’s journey with the Fraud Check application. It seems that good development starts with seeking out the right business opportunity.

“We look for places were Cloud Native can be applied. People say that everything can be moved into the cloud but that is not true—at least not yet. Our work as developers starts with identifying a market and a technology that is ripe for the change.

“FinTech is a big area where we think Cloud Native can be applied. The financial industry has traditionally preferred mainframe compute instead of cloud, because they have huge processing needs and occasionally have significant spikes in compute requirements,” says Vikranth.

By spikes Vikranth means the November and December jump in the number of transactions as people are out doing their Christmas shopping. (My apologies to you all for mentioning Christmas in early-October!)

“In reality, this makes FinTech companies ideal candidates for cloud. They can run a lower level of capacity throughout the year and then scale to need in peak times, without paying for the redundant server space the rest of the year,” says Vikranth. “But there is quite a lot of hesitancy in larger organizations.”

Luckily, FinTech is an industry with a phalanx of hungry start-ups waiting to attack. These young firms are most likely to go all-in on cloud from the very start. It offers a lower-cost business model that still offers the level of compute needed to compete with the big players.

By highlighting and helping start-ups go to the cloud, companies like HPE are able to show its value to the more established players and drag the whole industry along as the smaller firms act as proof of concept.

The HPE Cloud Native Development Team looked at the financial industry and decided to take on an existing solution. The HPE Card Authorization Solution, which allows faster and more comprehensive checks of card payments to speed up transactions but with heightened security—aiming to provide transactional approval with less than 1% of timeouts even in the winter months. The application is used by several banks to process transactions but is housed in a traditional mainframe.

The challenge for the Cloud Development Team was to rebuild the app from scratch. When taking something to cloud, it is not as simple as copying the existing application and housing it in a new place. Firstly, it is impossible to do and, even if one could manage it, the result would be full of bugs and not compatible with the new environment. However, the challenge of duplicating and then improving a whole application did not daunt the team. In fact, it seems to have been this challenge that made the project so appealing in the first place. They took the mainframe solution and, piece by piece, built a replica that could then be improved in the cloud.

This is all great but the really interesting part of the story for me was the masterplan to give the whole thing away. The HPE Card Authorization Solution is an example of evangelism and knowledge-sharing at its best. When they started the project, Vikranth and the team knew that it would not be their app to keep and maintain. That’s why, right from the early planning stages, they brought Java and .net developers from the FSI team into their own work and trained them up on cloud native.

At the start of the project these developers were total newbies in the Stackato world. Today, just 4 months after starting the project, they are the owners of their solution. Once the fourth iteration was complete, the Cloud Native Development Team passed the project on to the FSI developers they had trained. They continue to mentor them and give their advice and input when required, but it is a great example of how evangelism works: You only get to keep it if you give it away.

What comes next for the team will be more of the same—identifying an area where they can make a difference, then training others to help bring about that change.

Find out more about Stackato Evangelism by contacting Mudasser Zaheer.




About the Author


I manage the HPE Helion social media brand accounts promoting the enterprise cloud solutions at HPE for hybrid, public, and private clouds.I have put my toes in the ocean of cloud evangelism for the enterprise IT industry. But my expertise is in Social Media and Digital Marketing.

Jan 30-31, 2018
Expert Days - 2018
Visit this forum and get the schedules for online HPE Expert Days where you can talk to HPE product experts, R&D and support team members and get answ...
Read more
See posts for dates
HPE Webinars - 2018
Find out about this year's live broadcasts and on-demand webinars.
Read more
View all