Alex Barnes, Director of Cloud Hosting at Alfa, breaks down the myths, challenges, and real-world impacts of cloud transformation—and why the time to act is now.
In an era where digital agility can make or break a business, the debate over cloud adoption continues, especially in industries like equipment finance with complex legacy systems and strict compliance demands. In a recent Monitor Podcast, Monitor Editor-in-Chief Rita Garwood sits down with Alex Barnes, Director of Cloud Hosting at Alfa, to talk about the evolution of cloud infrastructure, why organizations hesitate to move, and what it really takes to make the leap. With over 16 years at Alfa and deep expertise in both on-premises and cloud deployments, Barnes offers a no-nonsense perspective on the current state — and future — of cloud transformation.
Rita Garwood: Let’s start with your background. What led you into cloud infrastructure, and how has your role evolved at Alfa?
Alex Barnes: So, I’ve been working at Alfa now for 16 years, and started out as a software engineer, working on our version 5 Java platform evolution. This was all back in 2011. This was when the cloud as we know it today was really just getting started. I was interested in the early platform-as-a-service offerings and was a beta tester of the Cloud Foundry private cloud product. And this was where I first proved that Alfa Systems version 5 was already architected to run on this type of cloud platform, almost without modification.
Garwood: Cloud adoption has come a long way. But many finance providers still run critical platforms on-prem. Why is that?
Barnes: I think the reality is that many old-school and critical applications like we see in our industry aren’t well-suited to running on modern infrastructures in a cloud environment since they just weren’t designed with that kind of deployment model in mind.
There can also be a belief that on-premises deployments are inherently more secure than those running in the cloud, but cloud platforms today are making it much easier to do the right thing from a security standpoint, right off the bat. Often, organizations just don’t have the resources to move critical workloads to the cloud, even if they want to.
Garwood: Do you see those same considerations holding back SaaS platform adoption?
Barnes: It can certainly sound big and scary, but when we talk to our customers about moving an existing Alfa installation to our cloud platform, we’re typically starting from the exact same version … I think trust is also very important here. SaaS vendors must work hard to gain and then retain the trust of their customers. The European Union’s Digital Operational Resilience Act, or DORA, has forced a step change in the way that SaaS vendors and their customers work together to verify resilience.
Garwood: What are the biggest misconceptions or fears that hold organizations back from cloud or SaaS?
Barnes: I think the biggest fears that we hear of are the loss of control, the security concerns, and then on top of that, just the overall cost implications of cloud and SaaS. These fears need to be mitigated by having the right organizational structures in place. For example, having a team that understands how to configure a cloud platform to meet security requirements.
Garwood: Let’s talk tenancy models. What are the pros and cons of multi-tenant versus single-tenant SaaS?
Barnes: Multi-tenant products are great for less critical products, but what this model doesn’t offer is the security, data residency or performance guarantees that are required for critical platforms. In a single-tenant platform, an issue might only impact one environment. Conversely, in a multi-tenant platform, some kind of issue is going to impact a lot of customers all at the same time.
We’ve taken some of the techniques used for multi-tenant infrastructure and applied them to the single-tenant model, which allows us to offer all those benefits of single tenancy while keeping the overhead contained.
Garwood: How does regulation — especially in finance — shape the cloud conversation?
Barnes: The major cloud platforms actually allow compliance requirements to be met through configuration. Our customers are often implementing Alfa systems using Alfa Cloud to ensure that they are meeting these rapidly evolving compliance requirements.
Regulatory bodies are moving to force companies to be more engaged in the capabilities of outsourced cloud services, certainly from a resilience standpoint.
Garwood: Some businesses feel too locked into their legacy architecture. How do you address that?
Barnes: A system which is locked into that legacy architecture is just going to cause more and more drag on future innovation. For highly custom in-house legacy architectures the key preparation for a cloud move would be assessing how those existing applications can be isolated and decoupled. Even if they really can’t move to the cloud, looking at those kind of opportunities will have a positive impact.
Garwood: How does the ‘I can fix it myself’ mindset evolve in a SaaS-first model?
Barnes: It’s a good customer-focused mindset, but by streamlining all deployments to be done the same way, they’re less likely to go wrong in the first place. The individual nature of self-managed installations overall makes support harder for all the teams involved and doesn’t necessarily result in better outcomes at all.
Garwood: In finance, downtime means lost revenue. How does Alfa’s Data Guardian help reduce that risk?
Barnes: Downtime is generally caused by a confluence of small but unexpected factors.
We’ve built Alfa Cloud with intra-region high availability. We’ve also worked on a range of options for disaster recovery. By storing customer backups across multiple isolated regions and cloud platforms, we know and regularly prove that we could rebuild a customer’s complete production infrastructure in a clean account in a matter of hours.
Garwood: For cloud-curious but hesitant organizations, what’s the first step?
Barnes: The key is to set up simple, low-impact, proof-of-concept exercises using non-production systems. At the end of that period, the infrastructure can simply be destroyed. There really is very little risk to a small-scale proof of concept.
Garwood: Beyond the technical, what cultural or organizational shifts are required?
Barnes: One of the biggest shifts for companies building their own cloud solutions is the requirement for teams to be aware of how their infrastructure usage impacts the monthly invoice. Organizations running these cloud workloads will need to start to talk about cloud FinOps. Companies will need to look for a balance. They’ll likely have their own engineering teams but also run any number of SaaS products for specific functions.
Garwood: What are signs that a company is overdue to shift to the cloud or SaaS?
Barnes: The main indicator is that the platform is starting to impact both compliance and innovation. As platforms age, it becomes harder and harder to support them, and an ever-increasing percentage of IT budgets are used to keep them running. It’s important to identify these sources of drag before they become a major problem.
Garwood: Without naming names, can you share an example of a successful shift?
Barnes: Where customers have moved from self-managed and on-premises installations, we’ve seen significant improvements in performance and issue resolution times.
The resilience argument is also very compelling. Cloud platforms allow for active configurations where both data centers are servicing customers in normal operation.
Garwood: And on the flip side, have you seen companies suffer from waiting too long?
Barnes: Yes. We’ve seen examples of customers stuck on legacy systems who were unable to rise to meet the needs of their customers during challenging times. Conversely, customers using modern cloud-native applications have been able to quickly roll out new tools and features, and our clients are able to grow their businesses very quickly during these times.
Garwood: What’s the one piece of advice you’d give an IT leader still debating cloud and SaaS?
Barnes: The most important piece of advice is to ensure that you have a clear set of success criteria for the move, and that you’ve engaged the right people and have the right plan to assess the outcomes. Continuous assessment is still needed. And by using containerized applications, you can make it easier to switch providers — or even move back to self-managed platforms — if the cost-benefit no longer makes sense.
