In my previous post, I briefly talked about event-based architecture for payment platform modernization and why the modernization is important to the industry. In this post, we will dive into details of the key capabilities to consider for the payment platform modernization. The capabilities covered in this post may not be the complete list but it definitely serves as a good start.
When the CODIV-19 pandemic started nearly 2 years ago, many were not prepared and suffered a great pain to maintain normal life, including the businesses… This is no different for the payment industry … the payment industry is one the most needing rapid innovation and change to stay ahead of competitions … the industry players need a new approach for their payment platform… Payment platform modernization is a journey and this journey will be less painful when you have done it right at the beginning
These open source tools are used by Red Hat to help their customers in digital transformation journey making the application modernization more achievable and easier compared to the past, with higher success rate.
Application modernisation is not just about the applications but also need to consider the impact of the modernising exercise to the existing internal costing and budgeting model (if any), governance processes & policies (or SDLC), the supporting services, the operation and application team, and the underlying application platform.
We all know Serverless, Function and Knative are meant to provide modern application platform for consumption based, faster start-up, lightweight, cost effective, event based, modular and etc. But how do they relates to each other and how they are different from each other. What do I need to know in order to help me to craft or choose the right solution for my organization needs.