Reply is the place to meet an incredible variety of enthusiastic, passionate, ideas-driven people, who want to make a difference and an impact.Would you like to know more?
This is Part 3 of our ten-legged journey to explore how the Cloud can enable productivity, innovation, and scalability in financial services.
Each of my ten blogs over the eighty days will echo the themes discussed in Reply’s ten-part webinar series,
Cloud in Financial Services, in which we’ll highlight some of the key points offered by our presenters and panel members.
In the second webinar, we benefited from a wonderful panel of experts who shared their ideas on strategic ‘infrastructure’ issues. If you haven’t yet read the second part, you can do so
In this blog, relating to the third leg of the journey, we are taking it one step further and discussing the ‘architecture’ of Cloud adoption. By this, we are referring to the blueprint that ensures that adoption of the Cloud reliably meets your business requirements.
I have summarised what I have learned from this third webinar’s collection of outstanding experts, including Patrick Devis, CIO of Belfius; James Saull, Senior Manager of Solutions Architecture - Global Financial Services, AWS; Tim Falla, Partner at Glue Reply; and John Sidhu, also a Partner at Glue Reply — subject matter experts in IT architecture.
Tim and John kicked off this third webinar talking about how
Glue Reply helps clients with Strategy & Architecture. They touched on seven key Cloud architectural considerations.
Figure 1: Driving an effective Cloud Architecture – Seven Strategic Considerations
With these 7 architectural considerations in mind, Tim and John noted the importance of the two architectural styles that underpin Cloud application, i.e.: APIs and Microservices (see Figure 2). James shared with us his experience with a range of financial institutions using AWS: Microservices architecture lets them make quick changes with minimal coding, encouraging a focus on business logic rather than the heavy lifting of building infrastructure that is required by legacy solutions.
Figure 2: Microservices and APIs are key architectural Styles that underpin Cloud-based Applications
“Moving to the Cloud is like buying a car. The car can drive you fast or slow and can get you where you want... However, once you bought it, you open the trunk and you see it’s full of gadgets...Then, the real tricky question is, ‘will I use them?’ And that’s not something you decide overnight without having had some kind of experimentation and experience.” — Patrick Devis, CIO of Belfius
Patrick shared an idea I wholeheartedly agree with, that the possibilities of the Cloud are almost endless but you have to learn what you can do before beginning to play with all the different ‘gadgets’. It begins as an IT ‘thing’ and, rapidly, the ‘Business people’ around the table begin to understand that it opens up wider business possibilities.
As a very simple example, let’s say you have a colleague who is fond of pushing live video streams to a million customers. Generally, you’d have to make a huge investment in infrastructure to make that possible. With Cloud, this becomes much easier and more affordable. It’s for that reason that IT and the Business must work together, because the IT team may not always identify, or be able to clearly express, the business opportunities that Cloud flexibility provides. Back to my opening comment: Your Cloud architecture is the blueprint that will ensure that your adoption of the Cloud reliably meets your business requirements!
Click here to watch the recap video for Webinar #3/10.
If you have any questions about any of the above, please feel free to reach out to us at Reply at