Tag Archives: Cloud

Cloud as a solution to legacy system problems (part 2): six steps to achieve Cloud migration

[January 9th 2017]

Cloud computing has a significant role to play in financial services as a strategic solution for resolving the problems of legacy systems. Here’s how financial institutions should approach Cloud migration.

In my previous article (The new IT experience: Cloud as a solution to legacy system problems in financial services), I argued that Cloud computing not only make sense in its own right, but it has an extra and significant role to play in financial services as a strategic solution for resolving the problems of legacy systems. The argument is that the process of migrating to Cloud will facilitate the large-scale rationalisation and decommissioning of (largely home-grown) problem systems that bedevil financial institutions. The previous article explained the benefits that can accrue from migrating to Cloud, while this article provides more information on how to undertake such a migration. As stated above, the main benefit of Cloud migration for financial institutions is the opportunity to rationalise systems, applications, databases, data sources, etc., and thus eliminate large amounts of the redundancy usually seen in such environments. By doing so, IT-based business operations will become easier and cheaper to deliver and support, as well as being more accurate, timely and secure. Data management will become easier and more reliable, while data quality can be assured in ways that are impossible with the current myriad of overlapping/duplicating (but never agreeing) data inputs and outputs. Not only do fewer systems and more accurate data make it easier and faster to make changes and fix problems, but Cloud computing is designed to facilitate truly agile development practices, with development and test servers being spun up quickly on demand (a process that can take months in other infrastructure models). Improved data management alone can be the difference between achieving and not achieving regulatory compliance. My recommended steps for planning and effecting Cloud migration are: assess current systems; design to avoid vendor lock-in; manage processes and culture; create a business case for change; avoid over-planning; and drop applications that are not Cloud-enabled.

  1. Assess current systems. Cloud migration should start with an audit of the entire systems infrastructure and a reassessment of applications and databases. An audit is a valuable opportunity to rethink the value and relevance of existing applications and decide which ones are worth modernising and reconfiguring; which ones should be replaced by new applications; and which are no longer relevant and should be retired. A major factor in rationalisation decisions is redundancy – the target should be to have only one software module for each required function (build once, use many), and for there to be only one ‘system’ providing one business service (internally or externally). This compares to the current model that will often see dozens (perhaps hundreds) of systems doing the same thing for different business segments (eg how many reporting systems or risk systems do you have in your organisation?). One factor on which to base rationalisation decisions is how easy (or not) an application can be enabled to work in the Cloud while providing the major benefits of the Cloud (scalability, availability, security, etc). Cloud enablement should not be taken for granted. Some applications will convert easily to being Cloud-enabled; while for others it will be more difficult and the business case for doing so will be weak or non-existent.
  2. Design to reduce vendor lock-in. Vendor lock-in is not in and of itself a bad thing (the vendors are providing great services), but it needs to be an active decision and not something into which you stumble unthinkingly. Avoiding lock-in and thus retaining the possibility of moving relatively easy from one major Cloud provider to another may make sense from a strategic perspective, but it can also reduce the benefits that can be realised from Cloud. There is certainly a case for going ‘all-in’ with a vendor and this maximising the benefits. For example, event-driven AWS Lambda compute functions are not portable outside AWS, but they do deliver significant benefits within AWS. By comparison, using universal instead of proprietary technologies will afford you more flexibility in future. Eg implementing your stack on an open-source PaaS (platform as a service) such as Mesosphere will make your architecture more ‘portable’, consuming only the infrastructure from the Cloud provider.
  3. Manage processes and culture. Technology develops faster than culture and processes. Opportunities offered by Cloud computing technology can give organisations incredible benefits, but only to the extent that processes and culture are supportive of the new practices. Superfast speed of infrastructure provision in Cloud can still run up against a wall of bureaucratic processes if you let it. Changing mind-sets is a huge determinant of Cloud success, and is something that is too often underrated or even overlooked.
  4. Have a business case. Don’t make migration an end in itself. Never do anything without a clear and compelling business case. Benefits you should be looking to validate and quantify include reduced capital expenditure; reduced operating costs; resources freed up to work on higher-value activities; increased development velocity; faster deployments to production; improved ease of support; reduced operational failure rates; improved data management and quality; increased transparency (monitoring, surveillance, reporting); easier to achieve regulatory compliance, etc.
  5. Don’t over-plan a long-term migration strategy. We all know that no plan survives first contact with the enemy. Instead, set goals and start moving toward them in a pragmatic and agile fashion. Remember that the environment will be changing around you (and the world of financial services has changed enormously in the past nine years), so what is important today might be less important tomorrow. Waterfall planned approaches simply store up risk for later on. Better to fail early with fewer consequences than go for big bang approaches to infrastructure change.
  6. Don’t migrate applications that are not fully Cloud-enabled. This is a big one as to do so merely replaces old problems with new ones. Continued availability of applications – one of the key reasons for migrating to Cloud – is an essential function of their Cloud readiness, and you won’t get this if the application is not enabled for Cloud. Simply having something sitting on Cloud infrastructure is not the same thing as it being Cloud-enabled.

Conclusion: Theories of evolution argue for two factors: random mutation and natural selection. The survival of organisations is also subject to these factors, except that they have to choose/engineer their own mutations while selection is done by clients and other stakeholders. In my opinion, Cloud is one of those mutations that in future will be demanded by stakeholders, from clients and shareholders to partners and regulators. As data protection, cyber security and cost-effectiveness become bigger and bigger factors in the environment, Cloud will move from being an option to being a business necessity. Knowing how to migrate to Cloud will become a differentiating factor in continued and future business success.

Cliff Moyce, January 2017.

This article was published first at Tabb Forum http://tabbforum.com/opinions/cloud-as-a-solution-to-legacy-system-problems-part-2-6-steps-to-cloud-migration 

Cloud as a solution to legacy system problems in financial services

[November, 2016]

Back in the days before centralised water and electricity, people had to dig their own wells and procure their own generators. As centralised infrastructure became available, it made sense to connect to the grid. Similarly, Cloud computing has now become that grid for business. It makes sense in its own right, but it has an extra and significant role to play in financial services and capital markets – that of strategic solution for resolving legacy systems problems.

The problems of legacy IT infrastructures in financial services and capital markets are many and manifest. On-premises, home-grown, self-managed infrastructures fail any modern objective measures of value for money, time and quality. They are expensive to operate; inflexible; opaque; hard and slow to support, enhance and test; insecure; difficult to scale; and, contain high levels of redundancy and obsolescence. When times were good, business divisions effectively (or actually) had their own IT divisions building their systems. Though it was incredibly inefficient from a corporate perspective (the corporation was often building the same systems over and over again from scratch) this “shadow IT” model allowed business units to respond quickly to opportunities and client needs (at least in theory). Since this time, budget constraints have forced financial institutions to integrate previously independent systems into something that can be operated, distributed and secured centrally. This has created a whole new set of problems. To try to fix or replace everything in the legacy systems infrastructure – and there have been many articles exhorting the industry to do just that (eg “by starting again with a clean slate”) – is to oversimplify the problem and to over-invest in the solution. The project is simply too big, expensive and risk-laden to contemplate. Further, it will not solve all the problems of building and running your own infrastructure, as it could simply replicate the model with ‘new legacy’. Yet, there is a strong need to align IT services to modern business operations, as many institutions are now facing the need to replace obsolete hardware in an IT estate that has been starved of money since the financial crash 0f 2008. Setting a strategic target of migrating infrastructure to the Cloud will force a large degree of rationalisation that might not otherwise be contemplated, thus reducing the problems of redundancy and support. It will also force adoption of an infrastructure that exemplifies best practice in all measures (flexibility, scalability, performance, security, sustainability, etc.) and will allow financial institutions to move onto more modern hardware, firmware, middleware, operating systems, databases and applications with little or no capital investment. Benefits of Cloud include:

  • Security. Although people tend to attribute security to physical possession, it is a common misconception and can be compared to holding money under a mattress as opposed to in a bank. In reality, Cloud is much more secure than any other option for infrastructure management and service delivery. The average on-premises infrastructure is penetrated multiple times a day, whereas the average big name Cloud provider may only have been penetrated a handful of times in its existence (they may claim it has never happened). Also, you cannot be as secure as you should be if any version of your firmware, middleware, operating system, databases, anti-virus, firewall, application software, etc., is not fully up to date (one high-profile, successful cyber-crime intrusion and financial theft in banking was enabled in part by a small group of servers having been overlooked for security software upgrades). Vendors and the open source community work hard to plug quickly any vulnerabilities uncovered in their products and services; but many of their customers are slow to implement essential upgrades (the worst that I have seen is a 10-year delay, but there are bound to be worse examples). The chances of an on-premises installation ticking all of the current version boxes is close to zero. Financial institutions just do not have the resources for monitoring, planning, and implementing new versions. The chances of a top Cloud vendor ticking the boxes is far higher – it is what they do for a living.
  • Cost. A big issue for enterprises is the high cost of running and maintaining IT infrastructure. A bank can spend up to 50% of its budget running IT-based business operations. Cloud computing offers near real-time, on-demand, subscription-based provisioning of almost infinite compute, storage and network resources, with the ability to scale up and down automatically, intelligently and in a matter of seconds. This provides the opportunity for huge increases in efficiency and productivity.
  • Availability. The reality of running on-premises data centres is that availability and recoverability is never guaranteed. Provided that applications are Cloud-enabled, continuous availability and disaster recovery are a function of the design and infinite horizontal scalability of the Cloud.
  • Speed of deployment. Applications designed for the Cloud and using Cloud services take significantly less time to build and deploy and are cheaper to run.

The benefits of Cloud listed above allow organisations to advance toward a more flexible, agile and data-driven model in several ways:

  • empowering agile approaches to development. By enabling self-service infrastructure acquisition, provisioning and deployment as well as elasticity and scalability, Cloud computing encourages innovation and experimentation, and speeds up continuous integration and delivery, empowering agile approaches to product, service or software development.
  • enabling data management and business intelligence. One of the bases of the digital economy – the availability of data and the ability to process data – is enabled and reinforced in the Cloud, which offers access to tools and compute power to process and consolidate Big Data and prepare them for specific tasks. Migrating data sources and data pipelines to the Cloud gives the technology team sufficient data and infrastructure elasticity to run predictive analytics and gather data-driven business intelligence.
  • improving the speed and quality of decision making.  Cloud plays a vital role in enabling faster and more informed decision making by providing broad and immediate access to data irrespective of their location, thereby reducing interdependencies between ‘information holders’. A strategy of migrating legacy infrastructure to the Cloud should have ubiquitous, transparent access to operational, process and customer data as an important objective. Current forced integrations of multiple systems (many doing a version of the same thing in an inconsistent manner) commonly create information silos.
  • freeing up resources and improving flexibility. Cloud can make an organisation ‘lighter’ and more flexible, as it allows a move from systems to services. This is especially relevant in modern heterogeneous computing environments with multi-tiered applications requiring a broad mix of technologies. Creating a ‘composable enterprise’ of software modules can become a reality if made an objective of migrating to Cloud. Resources that were previously invested in running and maintaining outdated technology can be re-directed to innovation in serving customers.

The above points are illustrated well by the global insurance group Ageas. The company adopted a Cloud-based enterprise platform that integrates the full range of back-end and front-end processes, from policy administration to claims and from finance to HR. As a result, the company’s processes are streamlined, operations agile and enterprise analytics easily accessed.

Conclusion

The financial services industry has available to it a strategic solution for large enterprise legacy IT architectures that if implemented correctly can free institutions from the limitations and implications of outdated technology. Cloud computing is much, much more than simply outsourcing the operation of your IT systems. It is a paradigm shift in how we think about and experience IT in our organisations. The benefits will be seen by customers, business users, IT developers, financial officers, operational executives, shareholders, regulators and many other stakeholders. Cloud is the future. Never forget: Every cloud has a silver lining!

Cliff Moyce, November 2016

This article was published first on Tabb Forum (www.tabbforum.com)